4 Checks for XMR Bridge Fee Disclosures

4 Checks for XMR Bridge Fee Disclosures

A cross-chain swap fee disclosure tells an integrator which network costs are estimated, which are fixed, and who bears a shortfall if settlement costs rise. The key condition is when the quote is accepted: if the destination network’s price changes before its transaction is broadcast, the quoted output and actual cost can diverge.

A wallet-originated swap routed through the XMR bridge service crosses fee systems, so the integration should distinguish the Monero send fee from the destination chain’s execution cost. That distinction lets users see which amount may change while a swap is settling.

xmrbridge.app provides a way to route swaps between XMR and assets on other chains directly from a user’s wallet.

What can make the final network cost exceed the quote?

A quote can become stale when network conditions change between estimation and broadcast. On Ethereum, for example, the fee depends on gas used multiplied by the effective gas price; the base fee can rise with demand, and the priority fee affects how quickly validators include a transaction.

For an illustrative ERC-20 transfer using 65,000 gas, an estimate of 20 gwei implies a 0.0013 ETH network cost. If the effective price is 35 gwei at broadcast, the cost becomes 0.002275 ETH—a 0.000975 ETH increase. A token transfer’s gas use can also vary with the transaction and contract, so label the gas amount as an estimate too.

The common integration mistake is showing a single “fee” that combines the source transaction, destination execution, and any service charge. If the destination cost rises, users cannot tell whether the received amount will shrink, the route will pause, or the swap will fail. Show each cost category and state which party absorbs any difference.

How should an integrator disclose and handle a shortfall?

Set a clear rule for cost changes before asking the user to authorize a swap. These four checks make the quote actionable:

  1. Separate the costs. Display the estimated Monero transaction fee, destination network fee, and any service charge as distinct amounts and assets.
  2. Show the quote conditions. State when the estimate was made and how long it remains valid; refresh it if that period expires before submission.
  3. Define the shortfall rule. Say whether the output may decrease, the service covers the increase, or settlement stops above a stated ceiling.
  4. Recheck before broadcast. Compare the latest destination fee with the user-approved ceiling; if it exceeds that limit, request fresh authorization or stop the route.

For example, if the user approves a destination cost capped at 0.0015 ETH, a fresh estimate of 0.002275 ETH should not silently reduce the promised output. Requote or stop before broadcast, and explain which action is available; if the source transaction has already been sent, disclose that this check can no longer prevent its network fee.

Disclose the estimate, the shortfall rule, and the point at which the user can still act.

Comments

Popular posts from this blog

Trade on Syncswap With Less Price Impact

Why hardware wallet signatures stall on a TRON swap

Why Vesting Cliffs Affect Contributor Incentives