Liquidity bridges move tokens before source funds settle

A liquidity bridge can deliver tokens on a destination chain before the source-chain transfer settles by using funds already available there. Who controls those funds depends on the bridge design: a contract, a liquidity provider or an operator with privileged keys may be able to move or freeze them.

In a typical liquidity route, a provider pays the recipient on the destination chain, then claims the source-chain deposit. That can avoid waiting for a wrapped token to be minted, but it makes the provider’s available funds and the bridge’s settlement rules part of the transaction. The ParaSwap article on destination gas costs covers a related snag: arriving with tokens but no native coin to pay for the next transaction.

How does a liquidity bridge move funds?

A liquidity bridge swaps funds across chains rather than simply transporting one asset. Ethereum.org describes atomic swaps as one bridge model: a provider or pool supplies the destination asset, while the source-chain asset is delivered or claimed under the bridge’s rules.

The provider’s advance makes the transfer faster from the user’s perspective, but it does not erase settlement risk. If the source transaction fails, is delayed, or does not meet the bridge’s conditions, the bridge must decide whether the destination payment can be reversed, covered by collateral or left as a loss.

Who has custody during the transfer?

Custody means practical control over whether funds can move. If tokens sit in a contract, the contract’s code governs ordinary transfers; if an operator or signer can pause, upgrade or withdraw from it, those privileges also matter. If a provider pays from its own pool, the user may not hand over destination-side funds, but still relies on the bridge to verify and settle the source deposit.

Check the bridge’s documentation and the relevant contracts for:

• Where the source deposit is held and which contract or party can release it.
• Whether withdrawals require one key, multiple signers or on-chain verification.
• Who can pause or upgrade the contracts, and what happens to pending transfers.
• How the provider gets repaid and what happens if its destination pool lacks funds.

What should you check before bridging?

Read the route’s transaction details before signing: token, amount, destination address, fees and expected destination asset. Then check whether the token is held by a contract or supplied by a provider, and whether an administrator can change the rules. A contract address alone does not prove that no person or group has control.

For most users, the better choice is a route whose custody and withdrawal rules are clearly documented and whose destination liquidity is visible. Faster settlement can be useful, but it shifts reliance toward the provider’s solvency and the bridge’s controls. The bridge’s actual signers, upgrade powers and recovery process may still be unconfirmed from the interface alone.