Account identity
Aperture derives and validates the public account under Sui rules. It does not assign a generic address from another network family.
Supported production mainnet
Sui in Aperture.
A network-aware home for SUI—with Sui addresses, fees, asset identity, transaction state, and safety boundaries kept visible.
Understand the network
Sui is not just a ticker.
Sui is a Move-based proof-of-stake network centered on owned and shared objects. Transactions name the objects they read or mutate, which allows the network to treat independent activity separately.
Address format. A 32-byte Sui address displayed as a 0x-prefixed hexadecimal value.
A Sui address can resemble other 0x-prefixed identities, but it is 32 bytes and must be validated under Sui rules.
Native asset and tokens
SUI is the native gas asset. Other coins and objects are identified through their package, module, type, and object data—not by a display ticker alone.
Fees and transaction state
SUI gas objects fund execution. A transaction digest identifies the transaction, while effects and checkpoint inclusion describe what the network finalized.
Mainnet boundary
This catalog entry is Sui mainnet. Aperture’s production catalog does not expose testnet balances, endpoints, or transaction routes.
Receive safely
The network is part of the address.
In Aperture, choose Sui and the exact asset before copying an address or QR code. The sender, exchange, or bridge must use the same mainnet. A matching symbol, logo, or familiar-looking string does not prove compatibility.
- Confirm the receive screen says Sui.
- Copy or scan the complete address; do not retype it.
- Check whether the sending service requires an additional memo, tag, or network-specific field.
- For a new route or meaningful amount, consider a small test transfer first.
- Keep the receive screen available until the sender has verified the same network.
Send deliberately
Review what the signature will authorize.
Aperture keeps asset selection, recipient validation, amount, fee review, authorization, broadcast, and finality as distinct stages. Before authorizing a transaction on Sui, review the full recipient, the SUI amount, and the network fee together.
Blockchain transfers may be irreversible. Aperture cannot cancel a confirmed transaction, recover an incorrect destination, or move an asset that was sent through the wrong network.
Transaction signing happens on the device. Public account data, fee requests, transaction history, and the signed transaction may reach network infrastructure; the private signing key is not part of the broadcast payload.
Verify independently
Use the right source for the right question.
Network documentationUnderstand Sui protocol rules
Public block explorerInspect Sui public chain state
Aperture JournalHow accounts and networks stay separate
Aperture JournalReceive crypto safely in Aperture
External documentation and explorers are independent public resources. Their availability, labels, and data are not controlled by Aperture.
Aperture for iPhone and iPad
One interface. 25 mainnets. No blurred boundaries.
Use Sui alongside Aperture’s other supported mainnets while keeping network identity, asset identity, fees, and transaction status explicit.