Why a destination swap can fail after a bridge
A failed destination swap can leave bridged tokens on the receiving chain; check both transaction records and the token balance before retrying or sending funds again.
3 min read
Markets, protocols and policy, reported
A failed destination swap can leave bridged tokens on the receiving chain; check both transaction records and the token balance before retrying or sending funds again.
3 min read
A transfer is complete only when the network confirms it and the receiving wallet credits it; track the sender record, transaction ID and destination balance.
3 min read
Native coins move in a signed transaction, while token approvals let contracts spend ERC-20 balances; the distinction changes the steps and permissions on-chain.
2 min read
Cross-chain swaps may subtract destination gas from the output because the service pays the receiving chain fee; check the net amount, fee basis and quote expiry.
3 min read
A stuck Mantle Bridge transaction usually needs a same-network replacement at the blocked nonce; clearing wallet activity alone does not cancel an on-chain transaction.
3 min read
A pending cross-chain swap is a sequence of transactions. Check the source receipt, bridge status, destination execution and final token balance to find its hold-up.
2 min read
A bridge quote’s destination amount is the number to compare: check the output token, route fees, slippage floor and network costs before signing.
3 min read