Bridge and liquidity: a careful practice guide

Two different actions

A bridge moves a supported asset representation between networks. Providing liquidity places an approved asset pair into a pool or position that other users may trade against. Neither action purchases a SmartDeed or guarantees income, price stability, or an exit.

During Alpha, use test assets only. The action page decides availability from the release and reviewed deployment evidence. A guide, venue name, reconstructed route, or visible button does not mean an integration is active.

Review a bridge transfer

• Check the exact source and destination networks, supported asset, amount, destination account, and fees.
• Check whether execution happens in your connected wallet or through an explicitly approved external handoff.
• Review the contract approval separately from the transfer. An approval does not move assets to the destination.
• Keep the source transaction and operation identifiers after submission.
• Wait for destination confirmation. Source confirmation alone is not a completed cross-chain transfer.

If the bridge is delayed

A relayer, validator, provider, or destination network may be unavailable even after the source confirms. Keep the original operation and check its state. Never treat a timer, a browser message, or a source receipt as proof of destination delivery.

Use the app's recovery path or official support. Do not follow a private message offering to release a stuck transfer in exchange for a recovery phrase, another payment, or a new approval.

Review a liquidity action

• Confirm the approved venue, factory, pool, pair, network, and exact contracts before approving tokens.
• Understand which assets you supply and which LP token or position represents the deposit.
• Review amount limits, expiry, slippage tolerance, token allowances, and network fees.
• For a concentrated-liquidity position, understand its price range and the possibility it stops earning trading fees outside that range.
• On withdrawal, verify the assets actually returned and the resulting position. A fee collection is not the same as withdrawing liquidity.

Know what the risks mean

Slippage is the difference between the expected and executed price. A slippage limit protects a boundary; it does not promise the best price or successful execution.

Changes in the relative prices of a pool's assets can leave you worse off than holding those assets separately, even when fees accrue. Thin liquidity, contract failures, changing prices, and network costs add risk.

Supported actions differ by venue. Some positions accrue fees into the LP asset; others have a separate collection action. Never assume Add, Remove, and Collect are available everywhere.