VERSE PRESS

Sui Unveils Tidehunter, a Custom Storage Engine Targeting a Core Validator Bottleneck

Mysten Labs has published research on a purpose-built database it says could replace RocksDB across Sui's validator network, delivering an 8.4-times improvement in write throughput over RocksDB in benchmarks and holding performance steady at throughput levels that exposed the current system's limits.

Sui Unveils Tidehunter, a Custom Storage Engine Targeting a Core Validator Bottleneck
|

Mysten Labs, the team behind the Sui blockchain, released a technical blog post and an accompanying academic paper in early 2026 detailing Tidehunter, a storage engine built from scratch to handle the specific data patterns that blockchain validators produce. The company says RocksDB, the widely used database Sui inherited from its early development, degrades noticeably around 6,000 transactions per second in validator testing. Tidehunter is designed to remove that ceiling, though a live production rollout date has not been announced.


The Problem With General-Purpose Databases

RocksDB was a reasonable early choice. It is a battle-tested system originally built at Meta, and using it let the Sui team focus on protocol design rather than storage infrastructure. The core issue is structural. RocksDB uses a Log-Structured Merge-tree architecture, which manages data by writing it to disk and then repeatedly reorganizing it through a background process called compaction. That compaction process consumes real disk bandwidth on top of whatever the live application is already writing.

Under Sui's validator workloads, Mysten Labs says RocksDB produced write amplification of 10 to 12 times. In practical terms, about 40 megabytes per second of application-level writes translated into 400 to 500 megabytes per second of actual disk activity. "Disk IO utilization was approaching saturation well before other system resources, even on high-end validator hardware backed by NVMe drives," the team wrote in its blog post.

This is not a Sui-specific failure. Aptos, Ethereum client teams, and Solana validator operators have all run into similar friction with RocksDB at scale. The RocksDB tuning documentation itself notes that high write amplification can constrain the maximum sustainable write rate.

Tidehunter is Mysten's answer to a problem the broader industry has been actively working to address. It is the second major validator-stack component Mysten Labs has targeted: the team addressed consensus latency first, with the Mysticeti v2 engine upgrade in November 2025.


How Tidehunter Works

The central design shift is treating the Write-Ahead Log (a running log databases keep to recover from crashes) as the permanent storage location, rather than a temporary buffer. In RocksDB, values get written to the log first and then rewritten again when the system reorganizes its sorted data files. Tidehunter writes each value once and keeps it there. A lock-free version of this log sustains roughly one million operations per second in testing, and the use of memory-mapped files eliminates a system call per operation.

When old data needs to be cleared, the engine deletes entire log files at epoch boundaries rather than running the continuous merge operations that make compaction so expensive. Benchmarks on one-terabyte datasets with one-kilobyte values show Tidehunter reaching approximately 830,000 write operations per second compared to roughly 99,000 for RocksDB, an 8.4-times improvement. The paper also benchmarks intermediate alternatives, with one engine reaching approximately 286,000 write operations per second, providing useful middle-ground context. Existence checks, which matter for read-heavy queries, came in 15.6 times faster than RocksDB, while point query speed improved 1.7 times over RocksDB, rounding out the read performance picture.

The paper was authored by five Mysten Labs researchers: Andrey Chursin, Lefteris Kokoris-Kogias, Alex Orlov, Alberto Sonnino, and Igor Zablotchi. It is available as a preprint on arXiv (2602.01873).


What It Means for Validators and Developers in Emerging Markets

The implications for infrastructure operators and developers in emerging markets are practical rather than abstract.

Validators currently need high-end NVMe hardware partly to absorb the amplified disk writes that RocksDB generates. If Tidehunter delivers its benchmarked 8.4-times write throughput improvement in production, the same hardware can sustain meaningfully higher throughput, or operators can achieve equivalent performance on less expensive equipment.

That matters in markets like India, which ranks first on the Global Crypto Adoption Index with a score of 1.00, where cloud infrastructure costs create real friction for new validator entrants. Nigeria ranks second on the same index, with a score of 0.64, and the West African region's developer ecosystem reflects that momentum.

For developers, predictable storage behavior affects DApp responsiveness. Sui's developer presence in West Africa has grown through SuiHub Lagos, opened in July 2025, with satellite activity in Ghana and Kenya. Africa saw 19.4 percent growth in crypto users in 2025, led by Nigeria, Kenya, and South Africa, reflecting a developer base that is expanding quickly. Adenyi Abiodun, a Mysten Labs co-founder, personally launched a fund to support Nigerian students training to become blockchain software developers.

These developers build on the same full-node and validator infrastructure (the network of nodes that process and store the chain's complete transaction history) that RocksDB currently strains at sustained loads. A stabler storage layer reduces the risk of unexpected latency spikes in production applications.

Sui's current network metrics give context for where the upgrade would land: the chain averages around 33 transactions per second in live usage, with a historical peak near 3,500. Its theoretical ceiling sits between 120,000 and 297,000 TPS according to network benchmarks. TVL stood near $1.04 billion as of January 2026, with a market cap around $3.52 billion.

Storage is among the infrastructure layers that will need to scale as the network approaches its theoretical limits.


What Comes Next

Tidehunter follows Mysticeti v2, Sui's consensus engine upgrade deployed in November 2025, which cut latency by 35 percent for Asia-based full nodes and 25 percent for European nodes. The pattern points to a systematic effort to address each layer of the validator stack in sequence: consensus first, storage next.

Mysten Labs has not published a deployment timeline. The blog post states that additional benchmarks and rollout details will follow. For now, Tidehunter remains a research-stage candidate. Developers and node operators watching Sui's infrastructure roadmap should treat a formal upgrade announcement, when it comes, as the relevant trigger for adjusting hardware or deployment planning.