How Sui Wallets Work
Sui does not keep a ledger of account balances, and it does not keep a pool of unspent outputs either. Everything on Sui is an object: a coin, a token, an NFT, a staked position, each with its own identifier, its own owner and its own version. Your wallet’s job is to know which objects you own and to construct transactions that consume and produce them. What looks like one SUI balance in the interface is really a set of coin objects the wallet has added together.
That design has consequences you can see in daily use. Transactions declare exactly which objects they touch, which is what allows the network to process unrelated transfers in parallel rather than queuing everything behind a single global order. Gas is paid in SUI, drawn from a specific coin object your wallet nominates, so a wallet with tokens but no SUI cannot transact at all — the same trap as every other network with a native fee asset, arriving through a slightly different mechanism. Wallets routinely merge and split coin objects behind the scenes to keep a usable gas coin available, and a wallet that manages this badly produces failures that read as bugs but are really housekeeping problems.
Storage is priced too. Creating objects costs a storage fee, and deleting an object you own returns part of it as a rebate, so cleaning up unwanted objects is not purely cosmetic. Addresses are 0x-prefixed strings, which looks familiar from EVM chains and is not the same thing — a Sui address is derived differently and a Sui wallet is not an Ethereum wallet with a network switch. Keys derive from a standard recovery phrase, but the derivation path and signature scheme are Sui’s own, so import compatibility between wallets should be verified rather than assumed.
One more mechanism worth knowing before it surprises you: sponsored transactions. Sui allows a third party to pay the gas for your transaction, which is how some applications let a brand-new user act without holding any SUI at all. It is genuinely useful onboarding, and it means the party sponsoring you sees and co-signs what you are doing.
zkLogin and Onboarding
Sui’s most distinctive onboarding route is zkLogin, which derives an on-chain address from an existing account with a mainstream identity provider instead of from a phrase you write down. You sign in the way you would to any app, a zero-knowledge proof establishes that you control that credential without publishing it on-chain, and an address you can transact with appears. There is no seed phrase to lose in the traditional sense, and for someone taking a first step into a self-custody-style wallet the friction reduction is substantial.
The trust model deserves to be understood rather than glossed over, because it is genuinely different from a seed-phrase wallet. Control of the address is tied to continued access to that identity provider account, combined with a piece of secret data — a salt — that the implementation must keep available to you. That means the recovery story shifts: instead of protecting a phrase, you are protecting an account and depending on whichever service manages the salt. Lose access to the provider account, or lose the salt, and the address can become unreachable. Providers can also suspend accounts for reasons unrelated to crypto, and implementations differ in how they store salts and how much they tell you about it.
Our position is that zkLogin is a reasonable way to start, try applications and hold small amounts, while a conventional key-based wallet remains the right home for balances that matter. If you use zkLogin, secure the underlying identity account seriously: a strong unique password, an authenticator app or hardware key for second-factor, and up-to-date recovery options on that account. And read the wallet’s documentation on where the salt lives and what happens if the service stops operating — a self-custody claim means little if one component of your recovery is somebody else’s server. The layered approach we recommend across the category, with small amounts in convenient wallets and the bulk behind stronger key custody, is set out in our comparison of wallets by security, coins and custody.
Wallet Options for Sui
Sui needs purpose-built wallet support: its object model, signature scheme and transaction format mean an Ethereum-style extension cannot simply add it as a network. In practice most activity happens in wallets built for Sui or in multi-chain wallets that have implemented it deliberately. What follows is drawn strictly from the specifications on file for the products we track; where Sui is not named, we say so rather than assuming coverage from a total chain count.
| Wallet | Type / platforms | Networks (as listed) | Sui in listed coverage | Price |
|---|---|---|---|---|
| Phantom | Extension + mobile, self-custody | Solana, Ethereum, Base, Polygon, Bitcoin | Not listed | Free |
| Trust Wallet | Mobile + extension, self-custody | 100+ chains incl. BTC, ETH, SOL, TON | Not named — verify in-app | Free |
| Exodus | Desktop, Mobile, Extension, self-custody | 50+ networks | Not named — verify in-app | Free |
| MetaMask | Browser extension + mobile, self-custody | Ethereum + all EVM chains; Snaps: SOL, BTC | Not listed | Free |
| Ledger | Hardware: Nano S Plus, Nano X, Stax, Flex | BTC, ETH, SOL + 100 chains | Not named — check current firmware docs | From $79 |
| Trezor | Hardware: Model One, Safe 3, Safe 5 | BTC, ETH + major chains | Not named — check current firmware docs | From $49 |
Custody is identical across the table — every entry is Self-custody (non-custodial) — and the four software products are Free, so what separates them here is whether Sui has been implemented at all. Expect to run a Sui-native wallet alongside whatever you already use for other chains, and check the ecosystem features you actually need — staking SUI with a validator, viewing objects rather than just token balances, and connecting to applications with clear signing prompts. Hardware coverage is granted per-asset and moves with firmware releases, so verify it in the vendor’s live documentation before buying a device for this purpose. The same per-asset caveat applies across newer networks, as we note in our Avalanche wallet guide.
How We Test and Rank Wallets
Installation comes from the developer’s own channel, never an advertised link, and we validate the file against any release signature the project publishes. A wallet is created, its phrase written out by hand, the app removed, and the wallet rebuilt from that paper on separate hardware. That round trip is a gate, not a bonus point: a wallet that cannot recover from the phrase it issued is not scored at all.
For Sui the specific checks follow the object model. We fund a wallet, send SUI and a token, and watch how the wallet handles gas coin selection when the balance is fragmented across several coin objects — this is where weaker implementations fail with errors users cannot interpret. We confirm the wallet displays objects and not only aggregate balances, delegate a small stake to a validator and unstake it, and check whether the app explains storage fees and rebates when they appear. Where a wallet offers a zkLogin-style login we record what it discloses about salt storage and recovery, because that determines whether the custody claim holds up.
Hardware claims are tested with the device connected: the address shown on the device must match the software, and the signing prompt must be legible rather than raw. Scoring weights recovery reliability, custody transparency and clarity of warnings over feature count. Published source code and independent review raise a score; opaque builds, hidden custody and silent signing lower it. Scores and badges are the review desk’s own conclusions, reopened whenever a vendor changes how keys, recovery or signing work.
How to Choose a Wallet
Work through it in sequence rather than starting from whichever wallet an application suggested.
- Size the balance first. Amounts you would be upset to lose belong behind a device that signs offline; experiment money can live in a browser extension or a zkLogin account.
- List the networks you use. Sui support is not something an EVM wallet adds with a network switch, so plan for a dedicated wallet alongside your existing one.
- Decide hot, cold or both. Hot means the key sits on a machine that connects to applications; cold means it lives on a device that only ever signs. Most people need both, sized by amount.
- Prove the recovery model before funding. Restore the phrase on a spare device — or, with zkLogin, establish exactly what recovery depends on — while the balance is trivial.
- Check hardware support for Sui specifically, since device coverage is per-asset and tied to firmware and companion-app versions.
Two Sui-specific filters are worth applying. Does the wallet show you objects, including staked positions and NFTs, rather than a single collapsed balance? And are signing prompts readable, naming what a transaction will do and which objects it touches, including when a sponsor is paying the gas? A wallet that reduces a programmable transaction to an unexplained confirmation button is the wallet that will eventually get you to approve something you did not intend. Staking here also works differently from the delegation model in our Cardano wallet guide, so read the wallet’s own documentation rather than transferring assumptions between chains.
Risks and Limitations
The blunt reality first: with a key-based Sui wallet, losing the recovery phrase means losing the funds permanently. No developer, validator or editorial team can restore it. Keep the phrase on paper or steel, apart from the device, and never photograph it, upload it to cloud storage or enter it into a page offering to verify or repair a wallet. With zkLogin the failure mode changes rather than disappearing: losing the identity account or the salt can make an address unreachable just as finally.
The active threats are familiar and effective. Malicious signature requests are the main one — a drainer front-end that imitates a real application can ask you to approve a transaction that moves your objects rather than doing what you clicked, and sponsored transactions add a party who co-signs alongside you, which is worth reading carefully rather than treating as free convenience. Fake wallet extensions and apps circulate, sometimes ranking above the genuine product, and a repackaged extension can produce keys its publisher retained. Unsolicited objects and tokens arrive with links or promises attached; interacting with them is where losses start. Anyone asking for a recovery phrase is attacking you, without exception.
Then there is ecosystem maturity, which cuts both ways and should be stated plainly. Sui is a younger network: tooling, hardware integration, audit history and third-party support are thinner than on the largest chains, fewer services recognise its addresses, and applications you rely on may change quickly or stop being maintained. Contracts written in a newer language have had less adversarial exposure than a decade-old codebase, and a wallet whose object handling is immature can leave you unable to transact until you consolidate coins. Liquidity for newer assets can be shallow. None of this is an argument against using Sui — it is an argument for sizing positions accordingly, keeping the bulk of long-term holdings in wallets with proven recovery paths, and remembering that careful key management does nothing about the market value of what you hold.
This page is editorial information, not financial, tax or legal advice. Crypto assets are volatile and balances held with third parties are not bank-insured. Availability, fees and terms change — verify with the provider before you sign up.