What is Sui, and what makes it different?

Why is this chain built this way, and what does that let apps do? That is a better starting point than memorising SUI’s ticker. Sui is a layer 1: a base network that records and orders transactions, keeps shared state, and provides the asset normally used to pay network gas. Wallets, games, marketplaces, and trading apps build on that base.

Sui’s distinctive choice is to represent many onchain things as objects. That choice affects how assets are owned, how transactions name their inputs, and how an app can combine several operations.

A layer 1 you can picture

An object has its own identity, owner or sharing rule, version, and history. A unique NFT is an easy mental model: it is not merely “one more number” in a balance. It is a particular thing with an ID that can move from one owner to another. A concert ticket could work the same way conceptually. Its object identity tells an app which ticket is being transferred, while the app’s rules can check its collection, event, or current owner.

This is why a familiar ticker is only a starting point. Two assets may look similar in a wallet but have different full coin types or different networks. The Sui object model documents the identifiers, owners, versions, and digests that make objects distinguishable. You do not need to learn Move before using Sui, but the object model explains why an app may ask for more precision than a symbol such as SUI or USDC.

Why objects can move independently

Objects also give Sui a useful way to reason about execution. Imagine Alice sending a ticket object to Bob at the same time that Carol sends an unrelated coin object to Dana. The two transfers do not need to edit the same piece of shared state, so the network can process them independently. Sui’s Move concepts describe this object-centric storage and the way transactions specify their inputs by unique IDs.

The benefit is architectural rather than magical. An app can tell the network exactly which objects an action uses, and unrelated actions have room to run in parallel. A shared object, such as a common pool or a game board used by many players, has a different coordination pattern. The design lets developers choose between private owned objects and shared state according to the application they are building.

One transaction can compose a workflow

Sui packages commands into a programmable transaction block, or PTB. Think of it as a small workflow whose commands execute as one signed transaction. A PTB can split a coin, call a Move package, pass the result into another call, and transfer an object at the end.

Here is a concrete example. An app could swap 1 SUI for USDC, take the USDC produced by that call, and transfer it to a specified recipient in the same PTB. The transfer uses the swap’s output rather than asking the wallet to create a separate second action. If either command cannot complete, the atomic transaction does not produce a half-finished result. Sui’s transaction payment documentation explains how PTBs compose operations across applications.

This composability is useful beyond swaps. A game can spend an object and mint a result, a marketplace can accept payment and transfer an item, and a finance app can route several calls while keeping their inputs and outputs explicit. The chain’s object model gives those workflows something concrete to pass between commands.

Gas pays for work and stored state

Gas is easier to understand when you separate two kinds of cost. Execution covers the computation validators perform: checking commands, running package logic, and updating state. Storage accounts for objects that remain part of the global state. A transaction that combines a swap with a transfer therefore needs a budget for the work of both commands, while a transaction that creates or changes persistent objects also has storage effects.

SUI is the usual gas asset, although Sui also supports sponsored transactions in which another account pays. The exact amount depends on the transaction and network conditions, so a general chain description cannot substitute for the gas information shown for a particular action.

What this changes for an app user

You only need one compact review before signing: confirm the Sui network, the exact assets or objects, the commands and recipient, the amount, and the gas details. On the current Sui Brokers Swap surface, that means reading the Bluefin 7K route, output, minimum received, slippage, and commission before your wallet signs. The first Sui wallet guide covers the network and signing basics, while the Swap guide follows the product flow.

Sui’s object model is therefore a design choice with visible consequences. It gives developers precise things to pass into an application, room for unrelated owned-object actions to run independently, and a transaction format that can compose a useful workflow. For a reader, that is the answer to “what makes Sui different?”: the chain is built around the things apps and users actually move, update, and combine.