Skip to the article
Onchain Brief

News from across crypto

Intent based bridge vs liquidity pool bridge: choose by size

Intent based bridge vs liquidity pool bridge: choose intents for speed on moderate transfers, and pools for steadier pricing when deep route liquidity can handle size.

The Onchain Brief Editors3 min read
Intent based bridge vs liquidity pool bridge: choose by size

Choose an intent-based bridge for speed on a moderate transfer, and a liquidity-pool bridge when a large transfer needs a predictable rate on a deep route. The first relies on a relayer to front funds; the second prices your transfer against liquidity already in its pools.

Speed and availability depend on different limits

Intent-based bridges can be fast, but a relayer has to choose to fill your transfer. A relayer is a third party that sends its own funds on the destination chain, then claims repayment later. Across is intent-based, and its relayers are repaid after UMA’s optimistic oracle settles.

That makes an intent route useful when you want to receive funds quickly and the amount is moderate. But a relayer may not fill every intent. When no relayer fills, the deposit is refunded, so you may need to try another route or wait.

Liquidity-pool bridges are available when the route has funds in its pools, but the pool’s depth caps what it can handle at a good rate. Stargate moves assets through per-chain liquidity pools. Its pricing depends on the liquidity available on the destination chain.

For moving ETH to Monad, compare an intent route with the Monad bridge by the amount you would receive. That comparison adds a concrete route for the same transfer, alongside the bridge design and its timing.

Price at size decides which route is worth it

Intent-based routes can suit small-to-mid transfers when the quoted amount and speed work for you. Liquidity-pool routes can suit larger transfers on deep routes, where the pool has enough funds to absorb the transfer without sharply worsening the rate.

Pool quotes worsen as the destination pool thins. A quote that looks fine for a small transfer may give you less when you move a larger amount. Before a large transfer, check the destination pool depth and compare the amount received across routes. The quote is more useful than a bridge’s general label.

Say you are moving a large amount of ETH to Monad. Compare the amount received through an intent route and the Monad bridge, and make sure the pool route has enough destination liquidity for your size. A thinner pool can make the pool route less attractive even when the route is available.

Across is an intent-based example, while Stargate uses pools; deBridge is another route name you may see when comparing options. Compare the actual quote, transfer size and whether a relayer will fill, rather than assuming every route behaves the same way.

Choose an intent-based bridge when speed matters and the transfer is moderate. Choose a liquidity-pool bridge when the transfer is large and the route has deep liquidity. For either design, compare the amount received for your specific transfer before sending it.