What Is Mysticeti? Sui's Consensus Protocol Explained
Mysticeti is Sui's DAG-based consensus protocol, committing blocks in three message rounds for about half-second finality. How it works, v2, risks and what it means for users.
Mysticeti is the consensus protocol that orders transactions on the Sui blockchain, a DAG-based Byzantine fault-tolerant design that commits blocks in three message rounds without certifying each block separately. It replaced Narwhal-Bullshark on Sui mainnet in July 2024, and it is the main reason Sui transactions that touch shared state usually finalise in around half a second.
Mysticeti at a glance
| Attribute | Detail |
|---|---|
| Category | Consensus protocol (DAG-based Byzantine fault tolerance) |
| Chain | Sui |
| Native token | None (validators stake SUI) |
| Launched | Research paper October 2023; Sui testnet May 2024; Sui mainnet July 2024; Mysticeti v2 default from Sui node v1.60 (announced November 2025) |
| Developed by | Researchers at Mysten Labs |
| Performance | About 0.5s average commit at 200,000 TPS in controlled benchmarks; Sui latency cut from about 1,900ms to 400ms in one 106-validator deployment (paper) |
| Security record | Peer-reviewed (NDSS 2025); Sui suffered a roughly six-hour halt on 14 January 2026 traced to a divergence in validator consensus processing |
| Website | docs.sui.io: consensus |
| Integrated with JewelSwap | Not an app: every JewelSwap transaction on Sui is ordered by Mysticeti, so there is nothing to integrate |
What is Mysticeti?
Every blockchain needs a way for validators to agree on the order of transactions. On Sui, that job belongs to Mysticeti. It was first described in an October 2023 paper by Mysten Labs researchers, including co-founder George Danezis, and later published at the NDSS 2025 security conference.
When Sui launched in May 2023 it used Narwhal and Bullshark, an earlier DAG-based pair developed by many of the same researchers. Narwhal certified every block with a round of signatures before Bullshark ordered them. That was robust but slow. Mysticeti dropped the explicit certificates, went to Sui testnet in May 2024 and reached mainnet in July 2024.
In November 2025 Sui announced Mysticeti v2, which folds transaction validation into consensus and adds a new client path called the Transaction Driver. It became the default from Sui node v1.60.
How Mysticeti works
- Everyone proposes at once. In each round, every validator proposes a block of transactions in parallel. That uses the whole network's bandwidth and makes it hard for any one validator to censor transactions.
- Blocks point to earlier blocks. Each new block references blocks from the previous round, so together they form a directed acyclic graph (DAG).
- Votes are implicit. Instead of collecting signed certificates for each block, a validator's reference to a block counts as a vote for it. That removes a whole layer of messages.
- Leaders commit in three rounds. Certain blocks act as leaders. Once enough later blocks support a leader, it and its history are committed. Mysticeti needs three message rounds, which the authors describe as the theoretical minimum for this kind of protocol.
- Owned objects take a fast path. Transactions that only touch objects owned by a single address don't need consensus ordering and can finalise faster.
Safety depends on validators holding more than two-thirds of staked SUI behaving honestly, the standard assumption for Byzantine fault-tolerant systems.
Key features
- Uncertified DAG. Skipping per-block certificates cuts the messages and signatures validators have to exchange.
- Minimum-latency commits. Three message rounds to commit, with blocks finalised as soon as the commit rule is met.
- Parallel proposals. Every validator contributes blocks each round, so throughput scales with the validator set rather than one leader.
- Transaction Driver (v2). Clients send each transaction to one well-placed validator rather than all of them. Sui measured end-to-end latency falling from about 0.55s to 0.40s on Europe-based full nodes and from about 1.00s to 0.65s in Asia.
- Immediate finality. Once committed, a transaction is final. There is no waiting for extra confirmations.
Risks and track record
- Liveness bugs. Consensus code is complex. On 14 January 2026, a divergence in how validators processed consensus left them unable to certify checkpoints for about six hours. Sui reported no certified transactions were rolled back and funds were never at risk.
- Upgrades around consensus. Not every halt starts in Mysticeti itself. Sui's November 2024 halt came from congestion-control code and its late-May 2026 outages from the v1.72 release, but a stalled chain looks the same to users either way.
- Stake concentration. The two-thirds honesty threshold is measured by stake, not by validator count. If a few operators hold most of the stake, the real security margin is narrower than the validator list suggests.
- Benchmarks vs production. The 200,000 TPS figure comes from controlled tests. Real-world latency depends on network load and where your RPC node sits.
What Mysticeti means for JewelSwap users
Indirectly, a lot. Mysticeti isn't something JewelSwap integrates with; it is the layer every Sui transaction passes through. JWLSUI mints, SJWLSUI stakes, farm deposits on Cetus and Turbos pools, and leveraged positions that borrow from Scallop all touch shared objects, so Mysticeti orders them.
In practice that means a confirmed JewelSwap transaction on Sui is final, typically within about a second, in line with the network-wide figures above. There is no reorg window to wait out before your deposit or stake counts. During a network halt, though, nothing confirms, so you can't add, withdraw or rebalance until the chain resumes. The products themselves are covered in JewelSwap on Sui, and validator economics in our Sui staking rewards guide.
Mysticeti vs other consensus designs
Compared with Narwhal-Bullshark, Mysticeti removes the certification step, which is where most of the latency gain comes from. Compared with Ethereum's proof-of-stake consensus, where blocks arrive every 12 seconds and full economic finality takes around two epochs, Mysticeti finalises in well under a second. The trade-off is a smaller, more tightly coordinated validator set. Our explainer on proof of stake vs proof of work covers the wider design space, and Sui validators explained covers who actually runs Mysticeti.
Fast finality matters most to apps that react to prices in real time, such as DeepBook's order book and Bluefin's perpetuals.
Related Sui apps
- Sui — the blockchain Mysticeti runs, and our directory of Sui apps
- Walrus — decentralised storage coordinated on Sui
- DeepBook — an on-chain order book that relies on low latency
- Bluefin — Sui's perpetual futures exchange
- Cetus — Sui's largest CLMM DEX
Learn more on the JewelSwap blog
- Sui validators explained — how Sui's validator set is chosen, staked and paid.
- Proof of stake vs proof of work — the two main ways blockchains reach agreement.
- Sui staking rewards and APY explained — where staking yield on Sui comes from.
Frequently asked questions
What is Mysticeti in Sui?
Mysticeti is Sui's consensus protocol. Validators propose blocks in parallel, build them into a DAG and commit them in three message rounds without separate certificates, which gives Sui finality of around half a second.
How fast is Sui finality with Mysticeti?
Sui's documentation cites an average commit of about 0.5 seconds in benchmarks. Sui's own measurements of Mysticeti v2 put end-to-end latency at about 0.40 seconds from Europe-based full nodes and 0.65 seconds from Asia.
Does Mysticeti affect JewelSwap?
Yes, indirectly. Every JewelSwap transaction on Sui, from JWLSUI mints to farm deposits, is ordered by Mysticeti, so it is final once confirmed. There is no separate integration because Mysticeti is part of the chain itself.
JewelSwap Sui Ecosystem directory · educational, not financial advice. Data as of October 2026. Browse all Sui apps.
