Safe Cross-Chain Transfer Checklist on Starknet
A pre-transaction checklist designed to reduce avoidable mistakes when bridging.
Why this matters on Starknet
A short pre-flight checklist can prevent irreversible mistakes. Network, token, recipient, route, fee and minimum received should all be confirmed before signing.
Starknet uses its own account and smart-contract environment, which differs from standard EVM networks.
Starknet does not follow standard EVM conventions. Address formats, token identifiers and approval mechanics differ, so EVM-oriented checklists and tools should only be applied to Starknet after confirming they are supported.
Starknet: what to pay attention to
- Costs: Check the current network cost and route mechanics before moving small balances.
- Security: Do not assume EVM contract and wallet conventions apply directly.
- Assets and tokens: Verify Starknet-specific asset and account details.
A Starknet checklist for this topic
- Compare the quote, the minimum received amount and the total fees before signing.
- Check that the token you hold on Starknet is supported for the route you are considering.
- Allow for a delay between sending and receiving; do not repeat a transfer while one is pending.
- Keep enough native balance on Starknet to pay for the transaction that starts the transfer.
Bridge from Starknet
Check the current network cost and route mechanics before moving small balances. On the Zora side: verify the token contract on Zora.
The bridge guide below is informational; any transaction depends on current network conditions and the route shown in the bridge interface.
Starknet → Zora BRIDGE GUIDE