Wallet Address Safety: Avoiding Simple Mistakes on Starknet
Best practices for copying, checking, and sharing wallet addresses before sending assets.
Why this matters on Starknet
A correct address on the wrong network can still produce a bad outcome. Copy carefully, verify the first and last characters, and confirm the destination network.
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
- Security: Do not assume EVM contract and wallet conventions apply directly.
- Assets and tokens: Verify Starknet-specific asset and account details.
- Costs: Check the current network cost and route mechanics before moving small balances.
A Starknet checklist for this topic
- Read what a Starknet transaction or signature request actually authorizes before approving it.
- Treat unexpected tokens or links that appear in a Starknet wallet as untrusted until verified.
- Review and revoke permissions you no longer use on Starknet, especially unlimited approvals.
- Check the domain you are on before connecting a wallet for any Starknet action.
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