Safe Cross-Chain Transfer Checklist on Fantom
A pre-transaction checklist designed to reduce avoidable mistakes when bridging.
Why this matters on Fantom
A short pre-flight checklist can prevent irreversible mistakes. Network, token, recipient, route, fee and minimum received should all be confirmed before signing.
Fantom provides an EVM-compatible environment with its own balances and token contracts.
Fantom uses EVM-style addresses and token contracts, which means the same address can hold balances on several EVM networks at once. A balance that is missing on Fantom may simply be sitting on a different network.
Fantom: what to pay attention to
- Costs: Compare network costs with route and liquidity costs.
- Security: Check the network and contract before interacting with unfamiliar assets.
- Assets and tokens: Verify the token contract on the selected Fantom network.
A Fantom checklist for this topic
- Allow for a delay between sending and receiving; do not repeat a transfer while one is pending.
- Keep enough native balance on Fantom to pay for the transaction that starts the transfer.
- Review the final recipient address and network before confirming a cross-chain transfer.
- Confirm both the source and destination network, including whether Fantom is one of them.
Bridge from Fantom
Compare network costs with route and liquidity costs. On the Cronos side: verify the Cronos token contract rather than relying on ticker alone.
The bridge guide below is informational; any transaction depends on current network conditions and the route shown in the bridge interface.
Fantom → Cronos BRIDGE GUIDE