Common Crypto Recovery Mistakes on Sui
The errors that can turn a simple wallet cleanup into an expensive transaction.
Why this matters on Sui
Recovery errors usually happen when users rush: wrong network, wrong token, wrong recipient, or a suspicious approval. A slower verification step is often cheaper than a correction.
Sui uses an object-centric model that differs from the account and token conventions of EVM networks.
Sui 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 Sui after confirming they are supported.
Sui: what to pay attention to
- Costs: Consider network transaction costs and route-specific costs when evaluating small balances.
- Security: Review transaction effects carefully and use trusted wallet interfaces.
- Assets and tokens: Verify the network-specific asset and object details rather than applying EVM assumptions.
A Sui checklist for this topic
- Estimate the complete cost of moving a balance from Sui: network fee, route cost and destination cost.
- Compare that cost with the balance value, not with the price shown in a portfolio tracker.
- Batch decisions when several small balances on Sui could use the same route.
- Leave balances on Sui that cannot be moved economically; they can be revisited later.
Bridge from Sui
Consider network transaction costs and route-specific costs when evaluating small balances. On the Aptos side: verify the network-specific asset representation and account details.
The bridge guide below is informational; any transaction depends on current network conditions and the route shown in the bridge interface.
Sui → Aptos BRIDGE GUIDE