Sui is a proof-of-stake Layer 1 blockchain whose mainnet launched publicly on May 3, 2023. It uses the Move programming language and represents on-chain state as objects. The SUI token is used for gas, staking, on-chain activity and governance-related functions described by the network.
The original version of this guide published unsupported transaction, gaming, TVL and price figures, claimed Move prevents whole classes of exploits, and recommended a portfolio allocation. Those claims have been removed. This version covers the design and the questions that developers and token holders should verify.
Sui’s object model
On Sui, assets and other state can be represented as objects with identifiers, ownership and version information. A transaction takes objects as inputs and may create, mutate, transfer or delete objects according to a Move package’s rules.
Ownership affects transaction processing:
- Address-owned objects belong to an address.
- Immutable objects can be read but not changed.
- Shared objects can be accessed by multiple users and require consensus ordering.
- Party-owned or other supported ownership forms can apply under the current protocol and application design.
Transactions involving independent owned objects do not all need a single global order. That allows parallel processing in suitable workloads. Transactions involving shared state still require coordination and can face contention.
It is therefore misleading to apply one theoretical transactions-per-second number to every Sui application. Throughput depends on transaction type, shared-object contention, validator hardware, workload and how finality is measured.
What Move changes
Move was designed around digital assets and resource-oriented programming. Types and module rules can make it easier to express constraints such as who may create an asset, how it can move and whether it can be copied or discarded.
Sui uses its own Move implementation and object APIs. Developers need to understand abilities, ownership, borrowing, dynamic fields, capabilities and package upgrades rather than assuming experience on another Move-based chain transfers exactly.
Move can prevent some mistakes at the language level. It cannot guarantee that an application is economically sound or bug-free. Developers can still implement faulty access control, oracle assumptions, arithmetic, upgrade logic or business rules. Bridges, front ends, wallets and off-chain services add separate attack surfaces.
An audit also covers a particular code version and scope; it is not insurance against all losses.
Consensus and staking
Sui uses delegated proof of stake. Validators process transactions and participate in consensus, while SUI holders can delegate stake. Voting power and rewards relate to stake under the network’s rules.
Research should examine:
- how stake is distributed among validators;
- validator commission and performance;
- delegation concentration;
- the consequences of downtime or misconduct;
- software and governance upgrade processes;
- how reward subsidies change over time.
Staking yield is not free return. Rewards may include issuance, and the value of SUI can move more than the reward earned. Custodial or liquid-staking services introduce additional counterparty and smart-contract risk.
Gas and the storage fund
SUI pays for computation and storage. Sui’s economic design includes a storage fund intended to account for the long-term cost of data kept by the network. Users can receive a storage rebate when eligible objects are deleted, subject to protocol rules and fees.
Developers should estimate both execution and storage effects. An application that creates large numbers of permanent objects can impose different costs from one that mutates compact state.
The gas price a user sees can also depend on reference prices and transaction details. “Low fees” in a general article should not replace a current transaction simulation.
SUI token supply
The total SUI supply is capped at 10 billion tokens. Only a portion was circulating at mainnet launch; additional tokens become available through releases, rewards and Sui Foundation programs.
The official token-schedule page publishes current circulation data and an estimated release chart. It also states that deployment of Foundation allocations can depend on network needs. That makes current official data more reliable than a fixed monthly-unlock number copied from an old article.
Token research should track:
| Item | Why it matters |
|---|---|
| Current circulating supply | Determines present market capitalization |
| Scheduled releases | Shows potential dilution timing |
| Community reserve | Identifies Foundation-controlled allocation |
| Mysten Labs and contributor allocations | Shows concentration and vesting exposure |
| Staking subsidies | Explains part of validator/delegator rewards |
| Treasury movements | Tests how disclosed allocations are used |
Fully diluted value assumes all 10 billion tokens at the current price. It is a comparison tool, not a forecast that every token could be sold at that price.
What gives SUI utility
SUI is needed to pay gas and can be staked. Applications may also use it for liquidity, collateral or payments. Governance may provide another reason to hold it under the applicable rules.
Network activity does not translate mechanically into token price. Low fees can mean many transactions create modest fee demand. Application users may prefer stablecoins, and token releases can outweigh new demand. A useful thesis quantifies these competing flows rather than listing wallet or transaction counts.
Ecosystem analysis without inflated metrics
Sui supports exchanges, lending protocols, liquid staking, games, NFTs and other applications. To evaluate an ecosystem, use several consistent measures:
- fees paid by real users;
- repeat users rather than one-time addresses;
- stablecoin and asset liquidity;
- developer activity and maintained applications;
- protocol revenue after incentives;
- concentration of TVL and volume;
- bridge inflows and outflows;
- security incidents and reimbursements.
An address is not necessarily a person, and a transaction can be generated automatically. TVL can rise because token prices rise. A game can send many transactions without producing sustainable revenue. Avoid ranking chains on one headline metric.
Sui compared with other Layer 1 networks
Comparisons with Solana, Aptos or Ethereum should start with the workload.
Sui’s object model can parallelize independent owned-object transactions. Solana uses an account model in which transactions declare relevant accounts, also enabling parallel scheduling when state access does not conflict. Aptos uses Move with its own execution and state architecture. Ethereum has a larger established application base and increasingly scales through rollups.
No chain is “faster” in every meaningful sense. Compare:
- sustained production throughput for the target transaction;
- time to economically meaningful finality;
- validator hardware and decentralization;
- fees during congestion;
- developer tooling and audit ecosystem;
- liquidity and bridge dependencies;
- outage and incident history.
User and investor risks
Token dilution
Future releases can increase circulating supply. Monitor the official schedule and actual circulation rather than relying on a static forecast.
Validator and governance concentration
Stake and large token allocations can concentrate influence. Review validator distribution and significant treasury holders.
Smart contracts and bridges
An application or bridge can fail even while Sui consensus works normally. Verify package IDs, administrator powers, oracle design and audits.
Ecosystem competition
Developers and liquidity can move to other networks. Technical design alone does not guarantee distribution, product demand or sustainable revenue.
Custody and scams
Fake tokens, wallet-drain sites and impersonated support accounts can cause irreversible loss. Verify the official domain and package or coin type, keep seed phrases offline and inspect every signature.
Price risk
SUI is a volatile crypto asset. A protocol milestone or partnership does not create a reliable price target. Do not use leverage or funds needed for essential expenses.
Developer due diligence
Before building on Sui:
- read current Sui Move and object documentation;
- model owned versus shared-object contention;
- test package upgrade and capability controls;
- estimate computation and storage costs;
- use supported SDKs and test environments;
- obtain independent security review for high-value code;
- prepare monitoring and incident-response procedures;
- make user transaction effects understandable before signature.
Bottom line
Sui’s distinguishing features are its object-centric state model, Sui Move implementation and economic design around gas, staking and storage. Those features can support parallel execution and asset-oriented applications, but they do not remove smart-contract, concentration, dilution or market risks.
Use official circulation data, test production performance for the actual workload and evaluate each application separately. SUI’s unit price and an unsourced TVL number are not substitutes for that analysis.
Advertisement
Sources and review
This article was checked against the primary or authoritative sources below on .
- Sui documentation — Sui
- Sui token supply and schedule — Sui Foundation
- Sui tokenomics — Sui Foundation
- Sui smart-contract platform economics white paper — Sui Foundation
Advertisement