BNB Smart Chain Dust Explained: Starknet Perspective
How small BEP-20 balances accumulate and what to consider before consolidating them.
Why this matters on Starknet
BEP-20 balances on BNB Smart Chain can be inexpensive to move, but unsolicited tokens can still carry contract risk. Separate legitimate leftovers from spam before consolidating.
BEP-20 tokens live on BNB Smart Chain. If you also use Starknet, the same ticker may be a different contract there, so compare the network and contract before treating two balances as the same asset. Verify Starknet-specific asset and account details.
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
- Re-check supported networks and tokens for any tool, since coverage changes over time.
- Identify which token standard and address format Starknet actually uses before applying any guide.
- Verify the exact token identifier on Starknet instead of trusting a shared ticker.
- Confirm your wallet is connected to Starknet so balances are read from the right network.
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