How to Perform a Basic Wallet Audit on Sui
A practical process for reviewing holdings, permissions, and unfamiliar transactions.
Why this matters on Sui
A basic wallet audit should be read-only first. Review balances and transaction history, then investigate unfamiliar contracts before taking any action.
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
- Assets and tokens: Verify the network-specific asset and object details rather than applying EVM assumptions.
- Costs: Consider network transaction costs and route-specific costs when evaluating small balances.
- Security: Review transaction effects carefully and use trusted wallet interfaces.
A Sui checklist for this topic
- List every asset visible on Sui and mark unfamiliar tokens for research instead of interacting with them.
- Compare each small balance on Sui with the full cost of moving it before deciding to consolidate.
- Keep a simple record of what you reviewed on Sui, 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 Sui.
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