On this page
Sui is a public Layer 1 blockchain built for applications that need to manage digital assets and update their ownership or state. Its native cryptocurrency, SUI, is used for network fees and staking. The design is distinctive because assets and application data are represented as objects with explicit ownership and access rules.
That sounds abstract until two users try to do unrelated things. When their operations do not depend on the same objects, a system can process work in parallel rather than force everything through one unnecessary bottleneck. When operations do share state, coordination still matters. Sui's design does not make conflicts disappear.
Who developed Sui, and where it stands
Mysten Labs developed Sui's core technology, and the Sui Foundation supports the wider ecosystem. Independent validator operators, wallet developers and application teams also participate. The network opened its public mainnet on May 3, 2023, following development and test-network stages.
As of October 16, 2026, Sui remains an active network with current developer documentation and continuing infrastructure releases. Its applications span areas such as finance, games and payments. The existence of a functioning network does not establish that every application on it has meaningful adoption or safe economics.
Institutional announcements also need their own dates and boundaries. Samsung's October 2026 stablecoin announcement includes Sui among its network partners, but the planned consumer rollout and the number of compatible devices are not the same as completed transactions or active users.
Objects change how contracts manage assets
Sui's object model distinguishes data that is owned by an address from data that must be shared or accessed under other rules. Each object has an identity and a version, helping the system determine which state a transaction intends to use. Contracts can describe how an asset moves and which operations are permitted.
The Move programming language is central to this approach. Its resource-oriented design helps developers express assets and restrictions on how they are handled. That is a tool for writing programs, not a proof that every program is correct. An application can still implement an unsafe pricing rule, give an administrator excessive authority or depend on bad external information.
A useful distinction is between a language preventing certain mistakes and an application doing what a user believes it does. The first can strengthen the development process. The second still requires examining the actual contract, permissions and surrounding service.
Consensus, parallel work and the meaning of speed
Sui uses delegated proof of stake: holders can delegate SUI to validators that participate in securing the network. Its consensus infrastructure includes Mysticeti, with continued development described in official technical material. The objective is to coordinate required ordering efficiently without imposing the same work on every possible operation.
Parallel processing can help when transactions operate on independent objects. A busy shared market or another heavily contested object creates a different workload. This is why a network benchmark cannot be read as a promise about every game action, exchange trade or payment made under real conditions.
Latency also depends on the full route. A wallet can be slow, a service can wait for additional checks, and an application can perform work outside the blockchain. A responsive interface is useful, but it is not an independent measurement of network finality.
Compared with Solana, Sui offers another approach to high-throughput application infrastructure. Comparing them meaningfully requires matching workloads, hardware assumptions, finality definitions and fee conditions rather than selecting the largest published number.
What SUI is used for
SUI pays for network resources and backs validator participation. A user executing an ordinary transaction generally needs to account for gas, while an application can use supported arrangements that change who pays. An interface that does not ask a user to acquire gas separately has not necessarily eliminated the underlying operational cost.
Delegating SUI gives a validator economic backing without requiring the holder to operate a node. The validator's commission and performance affect rewards. Delegation should not be confused with sending coins to an unrelated company promising a fixed return, or with buying a derivative that represents someone else's staking position.
Operational details matter around epochs, the periods used for validator and economic updates. A user's displayed staking status, eligibility for rewards and ability to withdraw should be checked through current supported software. A generic annual percentage is not a substitute for those conditions.
Gas includes computation and storage
Sui's fee model accounts for both computational work and the storage created by a transaction. Its storage-fund design is intended to compensate for the cost of maintaining data over time. Deleting eligible stored data can produce a storage rebate, subject to the protocol's rules.
This means a transaction's economics can differ from a simple per-transfer fee. Creating objects can add storage costs; deleting them can change the net charge. A rebate is not free money detached from an earlier storage obligation, and the maximum gas budget is not necessarily the amount ultimately consumed.
Users should review the transaction's intended changes as well as its fee estimate. The transaction-fee guide explains the broader difference between a resource budget, an actual charge and a separate service fee. A failed application action may still involve paid work, so a failure message does not automatically imply no cost.
Ten billion SUI does not mean ten billion circulating today
The Sui Foundation's supply page states a long-run limit of 10 billion SUI. A portion entered circulation at launch, with further tokens becoming available over time. The foundation describes the release schedule as proposed and responsive to the network's needs, so a chart should not be treated as an unconditional promise about every future date.
Supply questions therefore have several layers. The total allocation, the amount circulating, the amount staked and future releases are not interchangeable. A fixed ceiling can coexist with an increase in tradable supply when previously unavailable tokens are released.
The guide to crypto market data explains why those distinctions affect how market values are calculated. No release schedule alone can establish whether demand will grow quickly enough to absorb additional available tokens.
The main risks are wider than transaction performance
At the network level, users depend on correct software, sufficient validator participation and reliable access to infrastructure. At the application level, risks include contract errors, compromised administrative accounts, misleading token identities and bridges connecting different systems. A problem in one application should not automatically be described as a failure of every Sui component.
Wallet recovery and transaction authorization remain essential. A convenient login or sponsored fee does not make an asset reversible after it reaches the wrong destination. Before transferring, check the exact network, the supported asset and the receiving service's requirements.
Sui's object model provides a concrete way to understand its technical proposition. Whether that architecture serves a particular user well depends on the application built around it, the custody arrangement and the costs of completing the whole task. Those are more useful questions than treating speed, token supply or a large distribution announcement as a complete investment case.