Sui uses Move and an object-centric data model. Coins, packages and other onchain data are represented as objects with ownership rules. This differs from the account and contract storage model used by EVM networks, so a product needs a Sui-specific integration rather than a generic Ethereum connection.
Choose a Sui-native workflow
Start with Sui wallets for account access and transaction signing. Portfolio trackers can organize supported Sui assets and positions, while onchain analytics help inspect objects, addresses and transactions. Builders should verify support for Sui RPCs, Move packages and current SDKs among the developer tools.
Review objects, gas and permissions
- Network: mainnet, testnet and devnet are separate environments.
- Gas: standard user-paid transactions require SUI, although an application can sponsor gas in a clearly identified flow.
- Objects: a transaction may request access to owned or shared objects. Read the wallet summary and confirm what will change.
A wallet that only supports EVM chains cannot natively sign a Sui transaction. Always verify the exact Sui account and application domain before approval.
