Treasury Teams Need to Price the Fill, Not the Quote

For a treasury moving assets across chains, comparing relayer quotes means pricing the completed fill, not just the displayed fee. The useful comparison is what arrives on the destination chain, under which execution conditions, and for how long the quote remains valid.

A lower quoted fee can still produce a worse treasury outcome if it buys less output or depends on conditions the team cannot meet.

What does a relayer quote include?

A relayer quote prices the capital and execution needed to fulfill a transfer after the source-chain deposit is made. In an intent-based bridge, the relayer fronts funds on the destination chain, then seeks reimbursement through the protocol’s settlement process. Across’s documentation describes relayer fees as covering destination gas, the opportunity cost of capital and risks such as reorganization or delayed settlement.

Those costs sit alongside liquidity-provider fees, which compensate for pool utilization and rebalancing. Integrators may also add an application fee. That means a displayed total can combine charges with different recipients and drivers; treasury systems should preserve the breakdown instead of treating the total as a single relayer margin. For a fuller explanation of the transfer structures, the acrossbridge guide covers the distinctions that shape the quote.

How should treasury teams compare quotes?

Normalize each quote to the same input amount, token pair, source and destination chains, recipient, and transaction payload. Then compare the expected destination output and the conditions attached to receiving it. If the recipient is a contract, the calldata can affect the fill simulation and gas estimate, so quotes for a plain wallet transfer may not be comparable.

Across’s fee documentation describes quote responses that separate liquidity and relayer costs and can include an estimated fill time, amount limits and a low-amount flag. The quote timestamp also matters: protocol fee calculations may use utilization at that timestamp, while gas prices and available liquidity can move before execution. A treasury should record the response time and refresh the quote close to submission rather than carry an old estimate into an approval or signing workflow.

• Compare net output in the destination token, after all fees.
• Check whether the amount falls within the route’s minimum and maximum limits.
• Confirm any exclusive relayer, deadline or recipient-specific execution condition.
• Record quote time and expiry, then refresh before submitting the source transaction.

When is the cheapest quote the better choice?

The cheapest quote is preferable when its output, fill conditions and expected timing meet the treasury’s requirements. Where settlement timing is uncertain or an exclusive-fill window applies, compare those terms directly: a quote with lower fees may require more operational slack or create a different execution dependency. The right comparison is the cost of a transfer that completes under the treasury’s constraints.

For repeat transfers, retain the quote inputs and actual destination outcome. That allows the team to distinguish a pricing difference from a changed route, gas estimate or amount, and to set approval thresholds using observed executions. The decision rule is straightforward: price the amount delivered, confirm that the fill can occur as specified, and treat each quote as time-bound.