Wallet Address Safety: Avoiding Simple Mistakes on Sui
Best practices for copying, checking, and sharing wallet addresses before sending assets.
Why this matters on Sui
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.
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
- 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.
- Costs: Consider network transaction costs and route-specific costs when evaluating small balances.
A Sui checklist for this topic
- Send a small test amount first when an address or route on Sui is new to you.
- Verify the contract address on Sui from an independent source rather than a ticker or a logo.
- Read what a Sui transaction or signature request actually authorizes before approving it.
- Treat unexpected tokens or links that appear in a Sui wallet as untrusted until verified.
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