Sui: Node Types, Mempool & Finality Explained

Key Takeaways

• Sui uses Mysticeti v2 consensus protocol to achieve sub-second finality ranging from 250ms for simple transactions to 390-500ms for complex transactions
• The network operates two node types: validator nodes that participate in consensus and earn staking rewards, and full nodes that store blockchain history and serve RPC queries
• Sui’s DAG-based mempool architecture decouples transaction dissemination from ordering, enabling parallel processing and throughput exceeding 200,000 TPS in test environments
• Validator economics require significant capital investment (currently 30 million SUI, reducing to 2.247 million with SIP-39) but deliver competitive APY returns of 2.34% for operators
• The dual-path transaction system bypasses consensus for owned objects while routing shared objects through full consensus, optimizing both speed and security

Sui blockchain achieves transaction finality in under half a second through an object-centric architecture that separates simple transfers from complex consensus operations. This guide explains how Sui’s node infrastructure, mempool design, and finality mechanisms work together to deliver industry-leading performance for crypto miners evaluating validator opportunities and blockchain developers building high-throughput applications.

Understanding Sui Node Architecture

Sui blockchain operates through a distributed network of specialized nodes that maintain consensus, validate transactions, and serve data to applications. The network architecture divides responsibilities between two distinct node types, each serving critical functions in the blockchain ecosystem.

Validator Nodes: Consensus Participants

Validator nodes form the consensus backbone of Sui network. These nodes process transactions, participate in Byzantine Fault Tolerant consensus mechanisms, and collectively determine which transactions become permanently recorded on the blockchain. Validators must stake SUI tokens to participate, with their voting power proportional to their total stake including delegations from other token holders.¹

Running a validator node requires meeting specific hardware specifications: 24 physical CPU cores providing 48 virtual cores, 128 GB RAM, 4 TB NVMe SSD storage, and dedicated 1 Gbps network bandwidth. These requirements enable validators to handle Sui’s parallel transaction processing demands and maintain sub-second consensus commitments under network load.²

Validators earn rewards through multiple revenue streams. Transaction gas fees comprise the primary income source, supplemented by stake subsidies during the network’s early phase. The economic model provides validators approximately 2.34% APY on their staked tokens, with additional commission earnings from delegated stake. A validator maintaining the minimum 20 million SUI stake balance generates substantial returns in SUI tokens, though dollar-denominated values fluctuate with market conditions.³

Full Nodes: Data Infrastructure

Full nodes maintain complete copies of Sui blockchain history while serving read requests from applications and users. Unlike validators, full nodes do not participate in consensus or sign transactions. Their primary function involves validating blockchain integrity by re-executing transactions that validators previously committed.⁴

Full node hardware requirements remain more modest than validator specifications: 8 CPU cores, 32 GB RAM, and 2 TB NVMe storage suffice for basic operations. Production deployments handling substantial RPC traffic should allocate 16 cores, 64 GB RAM, and 4 TB storage to ensure responsive query handling during network congestion.⁵

Full nodes sync with validators to receive newly committed transactions, following at least two-thirds of the validator set to ensure they maintain accurate blockchain state. When validators commit a new transaction block, they push that block to all connected full nodes, which then validate the transactions and serve the updated state to querying clients.⁶

Node Types Comparison

Mysticeti: Sui’s Revolutionary Mempool Architecture

Sui blockchain implements a Directed Acyclic Graph-based mempool architecture that fundamentally differs from traditional blockchain memory pools. Rather than maintaining a simple queue of pending transactions ordered by gas price, Sui’s mempool serves as a data availability layer enabling parallel transaction processing.

From Narwhal-Bullshark to Mysticeti

Sui originally launched with Narwhal-Bullshark consensus, which separated transaction dissemination from ordering through a dual-protocol approach. Narwhal handled the mempool as a DAG of transaction batches, while Bullshark provided Byzantine Fault Tolerant consensus ordering. This architecture achieved impressive throughput exceeding 100,000 TPS but maintained latency around 2-3 seconds for shared object transactions.⁷

Mysten Labs deployed Mysticeti v1 to mainnet in July 2024, achieving an 80% latency reduction compared to Narwhal-Bullshark. The unified protocol eliminated the separate certification step for blocks, reducing round trips from three to just one and a half per consensus round. Mysticeti achieved consensus commits within three message delays, translating to approximately 390-500 milliseconds on wide area networks.⁸

The November 2025 rollout of Mysticeti v2 integrated transaction validation directly into consensus, eliminating the pre-consensus validation layer that added computational overhead. This integration delivered an additional 35% latency reduction, bringing complex transaction finality consistently below 400 milliseconds across global validator networks.⁹

DAG-Based Transaction Dissemination

Sui’s mempool organizes transactions into a Directed Acyclic Graph rather than a linear queue. Each validator proposes blocks containing transaction batches, with each block linking to previous blocks through cryptographic references. This structure enables multiple validators to propose blocks simultaneously, utilizing full network bandwidth and providing censorship resistance.¹⁰

The DAG architecture decouples data availability from consensus ordering. Validators broadcast transaction batches to build the shared DAG, ensuring all honest validators access identical data before ordering decisions occur. Consensus protocols then extract total ordering from this DAG without requiring additional transaction transmission, preventing throughput bottlenecks that plague traditional mempool designs.¹¹

Under controlled test environments with 50 validator nodes, Mysticeti maintains throughput exceeding 400,000 TPS before latency crosses the one-second threshold. Average consensus commitment occurs in approximately 500 milliseconds while sustaining 200,000 TPS in test conditions, significantly outperforming traditional consensus mechanisms that struggle to exceed 150,000 TPS at latencies starting around 2 seconds.¹²

Transaction Finality Mechanisms

Sui implements a sophisticated dual-path transaction processing model that optimizes finality time based on transaction complexity. The network achieves deterministic Byzantine Fault Tolerant finality, meaning committed transactions cannot be reversed or altered once confirmed by a quorum of validators.

Fast Path: Owned Object Transactions

Transactions involving only owned objects bypass full consensus through Sui’s fast path execution. Owned objects belong to a single address, enabling independent transaction processing without coordination across the validator set. Examples include simple peer-to-peer transfers, NFT minting from owned accounts, and token swaps from personal wallets.¹³

Fast path transactions achieve finality through Byzantine Consistent Broadcast rather than full consensus. The transaction submitter broadcasts to validators, collects signatures from a Byzantine-resistant quorum (greater than two-thirds of voting power), and aggregates these signatures into a certificate. Validators independently verify and sign the transaction without coordinating with other validators, enabling parallel execution across independent transaction sets.¹⁴

Sui’s fast path delivers finality in approximately 250 milliseconds under ideal network conditions. This sub-second confirmation enables use cases requiring immediate transaction feedback, such as gaming applications, retail payment systems, and high-frequency trading platforms. The fast path eliminates traditional blockchain block time concepts, providing instant economic finality for the majority of network transactions.¹⁵

Consensus Path: Shared Object Transactions

Transactions touching shared objects must traverse Sui’s full consensus mechanism. Shared objects allow multiple addresses to read and write simultaneously, requiring global agreement on operation ordering to maintain consistency. Decentralized exchange liquidity pools, multi-signature wallets, and collaborative game state represent common shared object use cases.¹⁶

Shared object transactions enter the Narwhal mempool as part of the DAG-based data availability layer. Validators batch these transactions, broadcast batches to form the shared DAG, and run Mysticeti consensus to agree on final transaction ordering. Once consensus commits the batch containing a transaction, validators execute it and finalize its effects on the blockchain state.¹⁷

Mysticeti v2 achieves consensus path finality in 390-500 milliseconds for shared object transactions. This performance enables real-time DeFi applications that previously faced multi-second latencies on other blockchains. Decentralized exchange swaps that required 2-3 seconds before Mysticeti now complete in under one second, dramatically improving user experience.¹⁸

Validator Economics for Crypto Miners

Sui validator operations present both significant opportunities and substantial capital requirements for crypto miners transitioning from proof-of-work infrastructure to proof-of-stake validation. Understanding the complete economic model helps miners evaluate whether Sui validation aligns with their investment goals and risk tolerance.

Entry Requirements and Costs

Current validator entry requires accumulating 30 million SUI in a staking pool. At current market prices of approximately $1.40 per SUI token, this represents roughly $42 million in capital requirements. The Sui Foundation operates a delegation program to help validators meet this threshold, though application processes remain opaque with limited public documentation available since the program’s 2022 announcement.¹⁹

SIP-39 proposal significantly lowers validator barriers by replacing the fixed SUI requirement with a voting power threshold. When fully implemented, validators need only accrue 3 voting power to join the active set. Voting power equals a validator’s stake divided by total network stake, multiplied by 10,000. At current total stake levels of approximately 7.49 billion SUI, 3 voting power translates to approximately 2.247 million SUI, or roughly $3.15 million at current valuations.²⁰

Hardware and operational expenses add ongoing costs beyond the staking requirement. Enterprise-grade dedicated servers meeting validator specifications cost approximately $500 monthly from providers like Cherry Servers or Hetzner. Including electricity, cooling, network bandwidth, and system administration overhead, annual operational expenses typically range from $8,000 to $12,000 for professionally managed validator infrastructure.²¹

Revenue Streams and Yield Analysis

Validators earn rewards through three primary mechanisms: transaction gas fees, stake subsidies, and storage fund redistribution. Gas fees provide the long-term sustainable revenue source, while stake subsidies (10% of total supply allocated over time) supplement early network rewards as transaction volume scales.²²

The Sui economic model distributes rewards at epoch boundaries, which occur approximately every 24 hours. Validators receive compensation proportional to their voting power share, modified by their Tallying Rule score measuring consensus participation quality. Rewards automatically compound into validator staking pools unless explicitly withdrawn by delegators.²³

With a minimum 20 million SUI stake balance generating 2.34% APY, validators earn approximately 468,000 SUI annually. The dollar value of these rewards fluctuates with market conditions—at $1.40 per token, this produces approximately $655,000 yearly revenue. Validators also collect commission rates typically ranging from 5-10% on delegated stake rewards, providing additional income scaling with total delegations.²⁴

“On-chain settlement latency just dropped significantly on Bluefin with the Mysticeti upgrade! P50 consensus latency currently is just under 400ms and E2E client latency when measured via a fullnode is under 1s for P50, which as far as I know is the fastest in Web3 right now – especially at scale with parallelization. With this upgrade, the trading experience on Bluefin has already become more seamless for retail, and our institutional partners have started to scale their flow and liquidity on the platform,” noted Rabeel Jawaid, Co-founder of Bluefin exchange following the Mysticeti deployment.²⁵

Risk Factors and Considerations

Validator operations carry several risk categories that crypto miners must evaluate. Slashing penalties apply when validators exhibit malicious behavior or extended downtime, potentially resulting in partial stake forfeiture. While Sui has not experienced major validator slashing incidents, the mechanism exists to maintain network security and validator accountability.²⁶

Token price volatility significantly impacts validator returns measured in fiat terms. A 2.34% APY generates predictable SUI rewards, but the dollar value fluctuates with market conditions. Validators must maintain 20 million SUI minimum stake or face removal after a seven-epoch grace period, requiring active position management during market downturns.²⁷

Technical competence requirements differ substantially from traditional mining operations. Validators must maintain 24/7 uptime, promptly apply software upgrades, monitor consensus participation metrics, and respond rapidly to network emergencies. The Sui Foundation expects validators to run nodes on both mainnet and testnet, participate in gas price surveys, and maintain communication channels for ecosystem coordination.²⁸

Finality Comparison: Sui vs Other Layer 1 Blockchains

How Sui’s Object Model Enables Fast Finality

Sui’s object-centric data model fundamentally enables its performance advantages over account-based blockchains. Rather than maintaining global state as key-value pairs associated with addresses, Sui represents everything as objects with unique identifiers, ownership metadata, and programmatic capabilities defined by Move smart contracts.

Object Ownership Types

Sui defines four distinct ownership categories for objects. Address-owned objects belong to a single Sui address and can only be modified by transactions signed by that address owner. Object-owned objects (child objects) require the parent object owner’s signature for modifications, enabling hierarchical asset structures.²⁹

Immutable objects cannot be modified by anyone after creation, but remain readable by all network participants. Move packages representing deployed smart contracts exist as immutable objects, ensuring contract code remains unchanged after deployment. Shared objects allow multiple addresses to read and write according to access control rules defined in the governing Move module.³⁰

This ownership model enables Sui to analyze transaction dependencies at submission time. Transactions touching only owned objects have explicitly encoded dependencies, allowing parallel execution without conflicts. The network can immediately identify which transactions require consensus (those touching shared objects) versus which can execute independently on the fast path.³¹

Parallel Transaction Execution

Sui processes multiple transaction groups simultaneously rather than forcing sequential execution. Transactions targeting different owned objects proceed in parallel across the validator network, eliminating the bottleneck where each transaction must wait for previous transactions to complete.³²

Move’s strong ownership types guarantee that parallel transaction groups cannot conflict. If two transactions attempt to modify the same owned object, the network detects the dependency and serializes those specific transactions while continuing parallel execution for all other independent transaction groups. This approach maximizes throughput without sacrificing consistency.³³

The object-centric approach also optimizes state synchronization. Rather than syncing entire account states, nodes track individual object versions. Each object carries a version number incremented with each mutation, enabling efficient tracking of which objects changed in each transaction. This granular versioning supports sparse replay and reduced storage requirements compared to account-based models.³⁴

Practical Implications for Validators and Developers

Sui’s architecture creates specific operational considerations for validators and development patterns for applications. Understanding these practical implications helps stakeholders make informed decisions about Sui infrastructure investments and application design choices.

Validator Performance Requirements

Validators must maintain consistent low-latency transaction execution to maximize rewards. The Sui Foundation monitors several performance metrics when making staking delegation decisions: participation rate in Narwhal proposal certification, sequencing latency for consensus transactions, and execution speed for owned object certificates.³⁵

Network participation requires running validator nodes on both mainnet and testnet environments. Testnet operation enables validators to test software upgrades before mainnet deployment, reducing the risk of downtime or misconfiguration that could trigger slashing penalties. Validators should implement automated monitoring through Prometheus metrics and configure alerts for consensus participation gaps.³⁶

Geographic distribution of validators improves network resilience and latency. Sui performs optimally when validators span multiple continents, reducing the impact of regional network failures and providing lower latency for globally distributed users. The Foundation’s delegation program tends to favor validators operating in underrepresented geographic regions.³⁷

Application Design Patterns

Developers building on Sui should carefully consider object ownership models during application architecture. Applications requiring maximum transaction throughput should minimize shared object usage, instead designing systems around owned objects and asynchronous coordination patterns. Gaming applications, for instance, can represent player inventories as owned objects while using shared objects only for marketplace interactions.³⁸

DeFi protocols must balance shared object convenience against performance considerations. A decentralized exchange pool implemented as a shared object provides atomic swap guarantees but requires consensus path execution. Alternative designs using owned object reserves with asynchronous settlement can achieve higher throughput for use cases tolerating slightly delayed finality.³⁹

Move’s capability-based security model requires developers to think differently about access control compared to Ethereum’s address-based permissions. Objects carry capabilities that grant specific operation rights, enabling more granular permission systems than simple owner checks. This model supports sophisticated multi-party coordination while maintaining the security benefits of explicit ownership.⁴⁰

Conclusion

Sui blockchain delivers industry-leading finality performance through an innovative combination of object-centric architecture, DAG-based mempool design, and optimized consensus protocols. The network’s dual-path transaction model achieves sub-second finality for both simple transfers and complex DeFi operations, setting new standards for blockchain responsiveness. Validators benefit from competitive economics despite high entry requirements, while full nodes provide essential infrastructure without staking obligations. As Mysticeti v2 continues optimizing latency and SIP-39 lowers validator barriers, Sui positions itself as the performance leader for applications demanding instant transaction confirmation across globally distributed user bases.

Sui Finality Mempool FAQs

How does Sui’s mempool differ from Ethereum’s transaction pool?

Sui’s mempool uses a Directed Acyclic Graph structure that decouples transaction dissemination from ordering, rather than maintaining a simple gas-price-ordered queue like Ethereum. This DAG-based approach enables multiple validators to propose transaction batches simultaneously, utilizing full network bandwidth while preventing the congestion bottlenecks that occur in traditional mempool designs where transactions wait in a sequential queue.

What is the difference between Sui finality for owned versus shared objects?

Owned object transactions achieve finality through Byzantine Consistent Broadcast in approximately 250 milliseconds, bypassing full consensus since these transactions have no dependencies on other concurrent operations. Shared object transactions require consensus path processing through Mysticeti, achieving finality in 390-500 milliseconds, because multiple parties can access and modify shared objects simultaneously, necessitating global agreement on operation ordering.

Can I run a Sui validator with less than 30 million SUI tokens?

Currently, validators must maintain at least 30 million SUI in their staking pool to join the validator set, though the Sui Foundation’s delegation program may help validators meet this threshold. However, SIP-39 proposal will reduce entry requirements to 3 voting power (approximately 2.247 million SUI at current total stake levels) when fully implemented, significantly lowering the capital barrier for new validators.

How does Sui achieve sub-second finality compared to other blockchains?

Sui achieves sub-second finality through several architectural innovations including its object-centric model that enables parallel transaction processing, Mysticeti consensus protocol that reduces communication rounds to the theoretical minimum, and dual-path execution model that bypasses consensus for independent transactions. These combined optimizations deliver deterministic finality 5-10x faster than traditional consensus mechanisms.

What happens to transactions during validator downtime on Sui?

Sui maintains Byzantine Fault Tolerance with validators possessing greater than two-thirds combined voting power remaining operational, meaning the network continues processing transactions even if up to one-third of validators experience downtime. Transactions submitted during partial validator downtime still achieve finality through the remaining validator quorum, though individual validator operators may miss rewards for epochs where they fail to participate in consensus.

Sui Finality Mempool Citations

1. Sui Network. “Validators.” Sui.io. Accessed December 2024. //sui.io/validators
2. Sui Documentation. “Validator Deployment and Configuration.” Sui Documentation. Accessed December 2024. //docs.sui.io/guides/operator/validator-config
3. Ekete, David. “How to Become a Blockchain Validator.” David Ekete Substack, June 2, 2025. //davidekete.substack.com/p/how-to-become-a-blockchain-validator
4. Sui Documentation. “Sui Full Node Configuration.” Sui Documentation. Accessed December 2024. //docs.sui.io/guides/operator/sui-full-node
5. Bacloud. “Sui Node and Validator Requirements 2025.” Bacloud Knowledge Base. Accessed December 2024. //www.bacloud.com/en/knowledgebase/279/sui-node-and-validator-requirements-2025.html
6. Sui Documentation. “Sui Architecture.” Sui Documentation. Accessed December 2024. //docs.sui.io/concepts/architecture
7. Encode Club. “What’s Sui? – Encode Club Sui Series #1.” Sui Blog, November 6, 2023. //blog.sui.io/encode-club-sui-series-1/
8. Sui Blog. “Mysticeti Set to Supercharge Consensus on Sui.” Sui.io, April 10, 2024. //blog.sui.io/mysticeti-consensus-reduce-latency/
9. Crypto News. “Sui Launches Mysticeti v2 Consensus Engine.” Crypto.news, November 7, 2025. //crypto.news/sui-launches-mysticeti-v2-consensus-upgrade-2025/
10. Babel, Kushal et al. “Mysticeti: Reaching the Limits of Latency with Uncertified DAGs.” arXiv preprint arXiv:2310.14821, November 2025. //arxiv.org/abs/2310.14821
11. Sui Documentation. “Consensus.” Sui Documentation. Accessed December 2024. //docs.sui.io/concepts/sui-architecture/consensus
12. Sui Documentation. “Validator Committee.” Sui Documentation. Accessed December 2024. //docs.sui.io/guides/operator/validator-committee
13. Sui Documentation. “Comparison.” Sui Documentation. Accessed December 2024. //docs.sui.io/sui-compared
14. Helius. “Compare Solana’s Transaction Lifecycle & Sui’s Object Runtime.” Helius Blog, August 12, 2025. //www.helius.dev/blog/solana-vs-sui-transaction-lifecycle
15. Sui. “Mysticeti.” Sui.io. Accessed December 2024. //sui.io/mysticeti
16. Sui Peera. “Deconstructing Sui’s Architecture: The Twin Engines of Narwhal and Bullshark.” Sui Peera, August 12, 2025. //sui.peera.ai/articles/3-0x46479ae03d9f19a86680037986c83b13f27fb7eb92a069e7e79c08a47ca52ef4/deconstructing-sui-s-architecture-the-twin-engines-of-narwhal-and-bullshark
17. Coinbase. “Guide to Sui.” Coinbase Developer Platform. Accessed December 2024. //www.coinbase.com/developer-platform/discover/protocol-guides/guide-to-sui
18. Brave New Coin. “Sui Sets The Standard for Blockchain Speed with New Mainnet Consensus Mechanism.” Brave New Coin, August 6, 2024. //bravenewcoin.com/insights/sui-sets-the-standard-for-blockchain-speed-with-new-mainnet-consensus-mechanism
19. Ekete, David. “How to Become a Blockchain Validator.” DEV Community, June 10, 2025. //dev.to/davidekete/how-to-become-a-blockchain-validator-4j7j
20. Sui Documentation. “Validator Deployment and Configuration.” Sui Documentation. Accessed December 2024. //docs.sui.io/guides/operator/validator-config
21. Cherry Servers. “How to Run a Sui Node [Sui Validator Requirements].” Cherry Servers Blog, May 12, 2025. //www.cherryservers.com/blog/sui-node
22. Everstake. “SUI Staking: Calculator, Yield, Rewards & APY.” Everstake, October 16, 2025. //everstake.one/staking/sui
23. Sui Network. “Validators.” Sui.io. Accessed December 2024. //sui.io/validators
24. 99Bitcoins. “Sui Staking: How to Stake SUI in December 2025.” 99Bitcoins, November 13, 2025. //99bitcoins.com/cryptocurrency/best-crypto-staking-coins/sui/
25. Brave New Coin. “Sui Sets The Standard for Blockchain Speed with New Mainnet Consensus Mechanism.” Brave New Coin, August 6, 2024. //bravenewcoin.com/insights/sui-sets-the-standard-for-blockchain-speed-with-new-mainnet-consensus-mechanism
26. CaptainAltcoin. “Sui Staking – Here’s How and Where to Stake SUI in 2025.” CaptainAltcoin, August 27, 2025. //captainaltcoin.com/stake-sui/
27. Sui Peera. “How to Stake SUI and Earn Passive Income in 2025.” Sui Peera, August 13, 2025. //sui.peera.ai/articles/3-0xc7f4b4a90503e24115c289e5536c3c4a8b3da8a0594e273fac85a8edd9310e86/how-to-stake-sui-and-earn-passive-income-in-2025
28. Sui Network. “Validators.” Sui.io. Accessed December 2024. //sui.io/validators
29. Sui Documentation. “Sui Architecture.” Sui Documentation. Accessed December 2024. //docs.sui.io/concepts/architecture
30. Coinbase. “Guide to Sui.” Coinbase Developer Platform. Accessed December 2024. //www.coinbase.com/developer-platform/discover/protocol-guides/guide-to-sui
31. Encode Club. “What’s Sui? – Encode Club Sui Series #1.” Sui Blog, November 6, 2023. //blog.sui.io/encode-club-sui-series-1/
32. Sui Documentation. “Comparison.” Sui Documentation. Accessed December 2024. //docs.sui.io/sui-compared
33. GitHub. “sui-playground.” GitHub Repository. Accessed December 2024. //github.com/abhi3700/sui-playground
34. Web3 Workshops. “Sui and Move.” Web3 Workshops. Accessed December 2024. //gimmi7.github.io/web3-workshop/sui_move.html
35. Sui Network. “Validators.” Sui.io. Accessed December 2024. //sui.io/validators
36. Sui Documentation. “Validator Committee.” Sui Documentation. Accessed December 2024. //docs.sui.io/guides/operator/validator-committee
37. Sui Network. “Validators.” Sui.io. Accessed December 2024. //sui.io/validators
38. Blog Sui. “All About Blockchain Infrastructure.” Sui Blog, May 22, 2024. //blog.sui.io/blockchain-infrastructure-explained/
39. Encode Club. “What’s Sui? – Encode Club Sui Series #1.” Sui Blog, November 6, 2023. //blog.sui.io/encode-club-sui-series-1/
40. Web3 Workshops. “Sui and Move.” Web3 Workshops. Accessed December 2024. //gimmi7.github.io/web3-workshop/sui_move.html