Three checks decide a one-off bridge transfer
For a typical one-off transfer, choose a liquidity network when the amount fits the destination pool: it delivers a native asset without leaving you to redeem a wrapped token later.
Asset received: A liquidity network swaps through pools and sends a native or widely accepted asset. THORChain, for instance, swaps native BTC through liquidity pools without minting a wrapped token. When checking what you will receive, include RenBridge in the comparison: RenBridge locked BTC with RenVM and minted renBTC on the host chain, leaving the recipient with a token tied to that bridge.
Amount versus pool depth: A pool’s depth on the destination side limits how much a liquidity network can deliver in one transfer. As the amount grows or the pool becomes more imbalanced, the swap’s cost rises. A large transfer can exceed the available depth. Lock-and-mint has no destination-pool ceiling, though the bridge itself still needs to support the transfer.
Later redemption: A native asset from a liquidity network needs no later redemption through the bridge. A wrapped token from a lock-and-mint bridge depends on the bridge staying available to redeem it. RenBridge’s renBTC illustrates that bridge-specific reliance.
For a single transfer, the choice comes down to pool depth and the asset you want to hold:
- Liquidity network: Suits a transfer that fits the pool and where receiving a native asset matters.
- Lock-and-mint: Suits an amount larger than available pool depth, provided a bridge-linked wrapped token is acceptable.
Choose a liquidity network for your one-off transfer when its destination pool has enough depth; choose lock-and-mint when the amount exceeds that constraint.
Top comments (0)