Set cross-chain slippage against each swap leg
Set cross-chain slippage against the quoted minimum output on each swap leg; bridge delay, route depth and failure handling determine how much headroom is safe.
5 min read
Protocol, chain and market reporting
Set cross-chain slippage against the quoted minimum output on each swap leg; bridge delay, route depth and failure handling determine how much headroom is safe.
5 min read
Bridge timing follows source-chain finality and the bridge’s verification threshold; a mined deposit alone does not prove destination execution.
5 min read
A nonce conflict means two transactions compete for one account sequence number; only one can land, and higher nonces wait until the gap closes on chain.
5 min read
RenBridge turned BTC into Ethereum renBTC through RenVM’s gateway and mint contract; its announced sunset makes redemption support the key question for holders.
4 min read
Moving trading capital across chains means choosing an asset representation and settlement path, funding destination gas, and verifying the credited token before trading.
5 min read
Cross-chain routers compare bridge paths, destination swap liquidity, fees and execution risk; the quoted pool is a snapshot, not a guarantee of final output.
5 min read
Budget a cross-chain swap by pricing execution on each chain separately, then account for route fees, destination actions and the possibility of a delayed leg.
5 min read
Bridge first when you need the same asset on another network; choose a cross-chain swap when the destination token matters, after checking route, output and recovery.
5 min read
On THORChain, a faster source-chain fee buys earlier inclusion, not a cheaper swap; its value depends on confirmation risk, quote limits and refund costs.
5 min read
A cross-chain swap can charge source gas, bridge and relayer costs, route spread and app fees; compare the minimum destination amount, not a headline rate.
5 min read