Wallet Network Mismatch: Common Causes on Starknet
Why a token can appear missing when the wallet is simply connected to another network.
Why this matters on Starknet
When a balance appears missing, the asset may simply be on another network. Checking the chain and token contract before assuming a loss is one of the simplest troubleshooting steps.
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
- Assets and tokens: Verify Starknet-specific asset and account details.
- Costs: Check the current network cost and route mechanics before moving small balances.
- Security: Do not assume EVM contract and wallet conventions apply directly.
A Starknet checklist for this topic
- Compare each small balance on Starknet with the full cost of moving it before deciding to consolidate.
- Keep a simple record of what you reviewed on Starknet, so the next checkup starts from a known state.
- Never enter a seed phrase or private key into a scanning or recovery site, including for Starknet.
- Leave a balance alone when the cost of moving it from Starknet exceeds what you would receive.
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