Solana's 100,000 TPS Debate: The Nature of an Ideal Experiment and Confidence in Performance Behind the Upgrade
TechFlow Selected TechFlow Selected
Solana's 100,000 TPS Debate: The Nature of an Ideal Experiment and Confidence in Performance Behind the Upgrade
The discussion about Solana's 100,000 TPS reflects experts' confidence in Solana's future upgrades to its client and consensus protocol.
Navigating Web3 tides with focused insightsAuthor: Haotian
Recently, discussions around Solana's 100K TPS have resurfaced, triggered by @cavemanloverboy actually achieving over 100,000 TPS on the Solana mainnet. However, most people don't fully grasp the meaning behind this figure:
1) First, Cavey's experiment was essentially a stress test under "ideal conditions." This does not represent Solana's normal mainnet performance and differs from lab results on testnets, though it's broadly similar.
He used a noop (no operation) program—meaning transactions only undergo basic signature verification and immediately return success, without performing any computation, altering account states, or invoking other programs. Each transaction was only 200 bytes, far smaller than typical transactions exceeding 1KB.
This means the 100K TPS result was achieved under non-standard transaction conditions. It measures the maximum throughput of Solana's network and consensus layers, not the actual processing capacity at the application layer.
2) Another key to this experiment's success was the Frankendancer validator client. In simple terms, Frankendancer is a "hybrid test version" of Jump Crypto's upcoming Firedancer validator—integrating Firedancer’s completed high-performance components into the existing Solana validator.
It effectively rebuilds Solana's node system using Wall Street-style high-frequency trading tech stacks, achieving performance gains through low-level optimizations like precise memory management and custom thread scheduling. Even partial component replacement delivers 3–5x performance improvement.
3) This experiment shows that under extremely ideal conditions, Solana can achieve over 100K TPS. So why is daily TPS only around 3,000–4,000?
In short, three main reasons:
1. Solana’s POH consensus mechanism requires validators to continuously submit vote transactions, which alone consume over 70% of block space, significantly limiting capacity for regular transactions;
2. Ecosystem activities often involve heavy state contention—for example, during NFT mints or new MEME launches, thousands of transactions may compete for write access to the same account, leading to high failure rates;
3. Arbitrage bots in the Solana ecosystem often flood the network with invalid transactions to capture MEV, resulting in resource waste.
4) However, the full rollout of Firedancer and the Alpenglow consensus upgrade will systematically address these issues.
A key feature of the Alpenglow upgrade is moving vote transactions off-chain, freeing up approximately 70% of block space for regular transactions while reducing confirmation times to 150 milliseconds—bringing Solana DEX experiences infinitely close to those of CEXs. Additionally, the introduction of local fee markets will prevent single popular applications from causing network-wide congestion.
Beyond performance improvements, Firedancer’s major benefit is enabling client diversity, allowing Solana to have multiple clients like Ethereum (e.g., Geth, Nethermind), thereby enhancing decentralization and resilience against single-node failures.
That's all.
Thus, knowledgeable observers see the Solana 100K TPS discussion as confidence in future client and consensus upgrades. The uninformed may use it as a TPS arms race to boost Solana’s visibility (though TPS comparisons are already outdated). But understanding the deeper significance behind this experiment offers real value. A quick explainer—shared here for everyone.
Join TechFlow official community to stay tuned
Telegram:https://t.me/TechFlowDaily
X (Twitter):https://x.com/TechFlowPost
X (Twitter) EN:https://x.com/BlockFlow_News
Haotian | CryptoInsight
