Instant Finality for Institutional Finance: A Builder's Guide to Settlement on Sui

September 2, 2026

6min read

Main Takeaways

Confirmation and finality are different states, and the gap between them is the latency an institution actually experiences. On a probabilistic chain a confirmed transaction can still be reorganized out, so institutions wait through several confirmations to approximate what Sui settles deterministically.
Sui settles transactions in roughly 390 milliseconds, keeps average cost under $0.02, and moves stablecoins gaslessly. Sub-second settlement is what makes point-of-sale payments, fast market making, and agent-driven workflows practical on-chain.
The speed comes from two design choices working together. Mysticeti's DAG-based consensus lets validators certify blocks in parallel and takes a fast path for simple owned-object transfers, and the object model lets independent transactions execute at the same time, so throughput scales with hardware instead of congesting.

Security decides whether an institution will put money on a blockchain at all. Once a chain clears that bar, the number that shapes what an institution can build on it is how long a transaction takes to become final. Final means the transaction is settled and can no longer be reversed. A payment that can still be reversed has not actually settled, however likely it is to stick. This guide explains transaction finality, why institutional finance should evaluate it closely, and how Sui's roughly 390-millisecond finality changes what is buildable on-chain.

Confirmation is not the same as finality

Confirmation and finality get used interchangeably, and the difference matters for anyone settling real value.

On many chains, a transaction is first included in a block, then waits as more blocks are added on top of it before it is considered safe. The early state is a confirmation. The transaction is probably going to stick, but under some conditions it could still be reorganized out. Finality is the point at which reversal is no longer possible. On a probabilistic chain, institutions wait through multiple confirmations to approximate finality, and that waiting is the latency they actually experience.

Sui provides deterministic finality. Once Sui settles a transaction, it is final, with no waiting period to reduce the odds of a reversal. For a treasury operation or a settlement system, that is the difference between a rail you can automate processes on and one you have to monitor by hand.

What 390 milliseconds makes possible

Sui finalizes transactions in roughly 390 milliseconds. For comparison, a chain that needs around 12 seconds to reach finality forces a person or a process to wait and watch before treating a payment as done, while sub-second finality settles fast enough to sit inside software that users expect to feel immediate.

Sui treats sub-second finality as the minimum bar for applications that feel as responsive as the software people already use. An application that takes seconds to confirm a payment cannot present itself as a real-time product. Once finality drops below a second, a category of financial applications becomes practical: point-of-sale payments that settle while the customer is still standing there, market-making strategies that depend on fast settlement, and agent-driven workflows that cannot tolerate multi-second waits.

The cost figures support the same use cases. Average transaction cost on Sui stays under $0.02, and stablecoin transfers are gasless, so moving them costs nothing at all. In benchmark testing the network has reached a theoretical peak of around 297,000 commands per second (CPS), the figure that counts the individual operations bundled inside transactions; that is a ceiling measured in testing rather than observed mainnet throughput. For institutional volume, low and predictable per-transaction cost, plus gasless stablecoin movement, are what keep high-frequency settlement economical at scale.

How Sui gets there: Mysticeti and the object model

Two architectural choices produce the speed, and both keep the speed durable as the network grows.

The first is the consensus protocol, Mysticeti, which runs on a DAG (directed acyclic graph) so validators can propose and certify blocks in parallel rather than in a single leader-driven line. Transactions that touch only owned objects, such as a straightforward token transfer, take a fast path that finalizes them without waiting for full consensus. The Mysticeti v2 upgrade folded transaction validation directly into consensus and added a streamlined submission path called the Transaction Driver, which cut latency further. Much settlement activity, moving value from one party to another, falls into exactly the category that takes the fast path.

The second is the object model. Sui treats each asset as a distinct on-chain object with explicit ownership rather than as an entry in a shared global account map. Because the system knows which objects a transaction touches, it can run transactions that do not share objects in parallel, with no risk of conflict. Independent payments do not queue behind each other. This is true parallel execution, and it is the reason throughput scales rather than congesting under load.

The scaling model follows from this. Most blockchains behave like a service with fixed capacity that raises prices when demand spikes and rations access when the network fills. Sui is built to scale horizontally: add more hardware and the throughput rises to meet demand, without congestion pricing. For an institution, that means the cost and speed it tests today do not degrade the first time the network gets busy.

Privacy and institutional readiness

Speed alone does not make a chain ready for institutional finance. Two other properties decide whether regulated entities can deploy: whether sensitive transaction detail can be kept private, and whether real institutional products already exist on the chain.

On privacy, Sui is adding confidential transfers, which keep a transaction's amount private on the public ledger. The sender and recipient stay visible, and the feature is in beta on devnet. Specific parties such as auditors or regulators can be granted visibility when a rule requires it. Position sizes stay off the public ledger, and settlement remains auditable for the people entitled to see it.

On products, Sui Dollar, the network's native stablecoin, is issued by Bridge (a Stripe company) and is designed to pass reserve yield back to the ecosystem. Hashi, a decentralized protocol for bringing Bitcoin into DeFi, is being built to let BTC holders earn yield or borrow without a taxable event, a point supported by a legal opinion, and without custodial trust assumptions. Hashi has not shipped yet. A global testnet is scheduled for July 2026, with more than 20 institutional partners signed on, among them BitGo, Ledger, Cumberland, and FalconX.

A checklist for evaluating a settlement chain

If you are assessing blockchains for institutional finance, the questions worth asking are specific and measurable.

Does the chain offer deterministic finality, or does it ask you to wait through confirmations to approximate it? How long until a transaction is irreversibly settled, measured in milliseconds, not block counts? What is the average transaction cost, and does it stay stable when the network is busy or rise with congestion pricing? Can transactions be made private while remaining auditable? And are there real institutional products and legal opinions in place, or only roadmap promises?

Sui answers these with deterministic finality of roughly 390 milliseconds, sub-cent average cost, gasless stablecoin transfers, horizontal scaling without congestion pricing, confidential transfers in beta on devnet, and institutional building blocks in Sui Dollar (issued by Bridge) and the forthcoming Hashi protocol for Bitcoin in DeFi.

FAQ

What is transaction finality and why does it matter for institutions?

Finality is the point at which a transaction is irreversible. Institutions care because a payment that can still be reversed is not a true settlement. Deterministic finality lets automated settlement processes treat a completed transaction as done without waiting through confirmation periods.

How fast is Sui's transaction finality?

Sui finalizes transactions in roughly 390 milliseconds with deterministic finality, compared with the multi-second or multi-confirmation waits common on older chains. Average transaction cost stays under $0.02, and in benchmark testing peak throughput has reached a theoretical ~297,000 commands per second (CPS), a testing ceiling rather than observed mainnet volume.

How does Sui achieve sub-second finality?

Mysticeti, Sui's DAG-based consensus, lets validators certify blocks in parallel and takes a fast path for simple owned-object transactions like transfers, finalizing them without full consensus. The object model lets independent transactions execute in parallel. The Mysticeti v2 upgrade integrated validation into consensus to cut latency further.

Is Sui suitable for compliant institutional finance?

Sui is adding confidential transfers (in beta on devnet) that keep transaction amounts private while leaving the parties and settlement auditable. Its institutional building blocks include Sui Dollar (issued by Bridge, a Stripe company) and the forthcoming Hashi protocol for Bitcoin in DeFi, the latter intended to avoid a taxable event per a legal opinion.