Sui wallet is a passkey-ready account interface for SUI

Crypto account interface for holding SUI, signing transactions, and using Sui apps, with passkey device authentication for simpler access.

Sui wallet is a passkey-ready account interface for holding SUI, approving transactions, and connecting to apps on the Sui blockchain. It gives a user one place to manage addresses, see coins and NFTs, review transaction details, and authenticate with device credentials such as passkeys where supported. The core job is simple: it turns a Sui address into a usable account for payments, DeFi, games, naming, and other Move-based applications.

Passkeys change the first step of using a Sui account

The distinctive part of the Sui user experience is authentication. Sui supports zkLogin, which connects familiar web credentials to blockchain accounts, and passkey-based device authentication, which uses the secure login features already built into phones, laptops, and browsers. That matters because many new users reach a dead end at seed phrases before they ever try an app. A passkey-supported flow lets account creation feel closer to unlocking a device than setting up an old-style crypto vault.

That does not remove the need to understand what a transaction does. It changes the way access begins. A Sui wallet still presents approvals, spending requests, signatures, and app permissions in a blockchain context. The cleaner sign-in layer is valuable because it reduces setup friction while keeping the account tied to cryptographic authorization rather than a password stored by an app.

What the account actually holds on Sui

A Sui account holds SUI, the native token used for gas and network activity, along with other assets created on the chain. Those assets include fungible tokens, NFTs, game objects, and app-specific items built with Move. Sui uses an object-centric data model, so a wallet view is more than a balance screen. It reflects owned objects that applications read, mutate, transfer, or display.

This is why a Sui wallet feels especially relevant for gaming, collectibles, and onchain identity. An item in a game, a SuiNS name, a token position, and a plain SUI coin all live as assets connected to an address, though apps present them in different ways. The wallet is the place where ownership becomes visible before an app asks for permission to use it.

How approvals, signatures, and gas fit together

Every blockchain account needs a way to say yes or no. On Sui, apps request signatures for actions such as sending SUI, minting an NFT, swapping through a DeFi venue, staking, or updating an owned object. The wallet shows the request, the connected site, the account involved, and the expected effect. A user then approves with the configured authentication method.

Gas is paid in SUI unless a sponsored transaction covers the fee. Sponsored transactions are important for consumer apps because they let builders hide or absorb gas in specific workflows, such as onboarding, game actions, or promotional mints. When gas appears in the wallet, it represents the network cost for executing and storing the transaction, not a separate service charge from the interface itself.

Using Sui apps from one account screen

The practical workflow starts with choosing an account, funding it with SUI, and connecting it to a Sui app. Once connected, the same address works across DeFi, payments, games, NFT markets, and identity tools that support the Sui wallet standard. A user signs only when an app needs authorization, so browsing an app and signing a transaction are separate moments.

A typical first session looks like this:

• Create or import a Sui account through a supported wallet interface.
• Add SUI for gas, or use an app flow that sponsors the first transaction.
• Connect the account to a Sui application and review the requested permissions.
• Read the transaction summary before signing a transfer, swap, mint, or stake action.
• Confirm the result in the activity history after the network settles it.

This rhythm keeps the wallet close to the action without turning it into the app itself. The app builds the transaction; the wallet makes the account, assets, and approval step visible.

Where SUI, USDC, DeFi, and NFTs appear in the wallet

Sui has native SUI for gas and network participation, and it also supports assets used across payments and DeFi. USDC is part of the Sui ecosystem, and Sui's own materials highlight gasless stablecoin transfers as a user benefit. In a wallet interface, stablecoins and other tokens appear as balances attached to the same account, while DeFi positions surface through the apps that created them.

DeepBook, Sui's programmable liquidity layer, gives builders a native venue for order-book-style liquidity. Wallet users encounter it indirectly through trading apps and aggregators rather than by managing DeepBook itself. The same pattern applies to NFTs and game items: the wallet proves ownership and signs movement, while specialized marketplaces and games provide the richer interface for discovery and use.

Security choices a user makes before signing

Security starts with account access, then continues through transaction review. Passkeys and zkLogin improve the login path, while hardware wallets, recovery methods, and separate accounts help users organize risk. A small spending account for games or new apps and a separate account for larger holdings gives clearer boundaries than placing every asset behind one approval surface.

The most important signing habit is reading the action, recipient, and asset before confirming. If a request looks different from the button that triggered it, stop and inspect the app connection. This single pause catches the common mistake of approving a broader action than intended, especially around unfamiliar NFT mints, token claims, and swap routes.

Recovery and account portability

Recovery depends on how the account was created. A seed phrase account relies on the recovery phrase and the wallet software that imports it. A passkey or zkLogin account follows the recovery model attached to the credential provider and device setup. The difference matters because losing a phone, browser profile, recovery phrase, or cloud credential affects the account in different ways.

Typically, Sui wallet choices should be made with recovery in mind before assets are moved. Users who prefer portable self-custody often keep a seed phrase or hardware-backed account. Users who prioritize simpler onboarding often choose passkeys or web-credential flows where supported. Both models lead to Sui addresses; the access and recovery assumptions are the part that changes.

Wallet alternatives inside the Sui ecosystem

There is more than one way to manage a Sui account. Browser extensions suit desktop DeFi and developer workflows because they sit beside web apps. Mobile wallets fit payments, collectibles, and passkey-first onboarding. Hardware-backed setups serve users who want a stronger separation between daily browsing and signature authorization.

The right choice follows the activity. A player wants fast app connection and readable item views. A DeFi user values clear transaction previews, account separation, and token visibility. A builder tests with development accounts, faucets, and Sui tooling before preparing production flows. In each case, Sui wallet functionality is the bridge between the address and the app, but the best interface is the one that matches the transaction pattern.

Why this matters for everyday Sui use

In most cases, Sui is built around low-latency execution, Move smart contracts, and a modular stack that includes authentication, data, identity, liquidity, and developer tooling. Wallet design decides how much of that stack feels reachable to normal users. When account creation is quick, asset ownership is legible, and transaction prompts are understandable, more of the network becomes practical beyond technical audiences.

A Sui wallet therefore works as the daily control panel for a Sui address. It holds the account together across SUI gas, tokens, NFTs, app permissions, passkeys, zkLogin, and activity history. The strongest setup is simple enough to use often and structured enough to keep approvals, recovery, and higher-value assets under deliberate control.