Contenu source (brut)
<p>Many thanks to 0xIchigo and Brian Wong for reviewing earlier versions of this work.</p><h2>Introduction</h2><p>The Agave v3.0 major release marks another milestone for Solana, introducing a range of upgrades aimed at improving network performance, validator operations, and the developer experience.</p><h3>Notable Agave 3.0 Updates </h3><ul class="list-bullet"><li value=1><strong>Cache Overhaul</strong>: delivering 30–40% faster transaction processing</li><li value=2><strong>Higher Single-Account Compute Limit</strong>: raises the single account limit to 40% of a block’s CUs</li><li value=3><strong>New Scheduler TransactionView Struct</strong>: improving scheduling efficiency</li><li value=4><strong>eXpress Data Path (XDP) for Turbine:</strong> a prerequisite for 100 million CU blocks</li><li value=5><strong>Increased CPI Nesting Depth</strong>: raises the CPI nesting limit from 4 to 8</li><li value=6><strong>Relax Entry Constraints</strong>: simplifies scheduling logic and is necessary for async execution</li><li value=7><strong>Faster Startup Times: </strong>nodes now come back online faster</li><li value=8><strong>Loaded Transaction Data Size Specification: </strong>standardizes how loaded transaction data is calculated</li><li value=9><strong>RPC Improvements: </strong>faster, more reliable real-time updates for dApps using PubSub WebSockets</li></ul><p></p><p>Each section of this article is self-contained, allowing readers to focus on the topics most relevant to them. Whether you’re a validator operator, developer, or active community member, this guide to Agave v3.0 offers you the key updates and insights needed to make the most of the latest improvements.</p><h2>Client-Related Trends</h2><p>Before exploring the details of Agave v3.0’s new features, let’s look at how recent data highlights the progress made by the Solana network and the Agave client, showcasing faster release cycles, broader client adoption, and robust performance under pressure.</p><h3>Agave Release Cadence</h3><p>Anza has notably accelerated its release cadence this year, reducing the gap between minor Agave versions to under three months. The Agave 2.2.* series remained the supermajority version for only 11 weeks, with Agave 2.3 tracking a similar timeline.</p><p></p><img src="/_next/image?url=/api/media/file/agave-client-version-number-of-weeks-as-supermajority.PNG&w=3840&q=90" alt="Agave client version number of weeks as supermajority" /><p></p><h3>Multi-Client Network</h3><p>Firedancer adoption on mainnet has advanced significantly in recent months. Currently, 21.6% of stake is running the Jito-Frankendancer client, a figure that has grown slowly and steadily throughout the year (see chart below). Adoption is expected to remain around the 20% threshold until the full Firedancer client is production-ready for mainnet deployment.</p><p></p><img src="/_next/image?url=/api/media/file/client-adoption-by-stake.PNG&w=3840&q=90" alt="Client adoption by stake" /><p></p><p>This marks a significant milestone for Solana’s multi-client strategy, a long-standing goal aimed at improving network safety, liveness, and resilience. Increased client diversity offers greater choice to validator operators, fosters healthy competition among client teams, and brings more eyes to the client codebases. It also mitigates the risk of a single critical bug triggering a network-wide outage.</p><p></p><p>It’s also notable that stake running the vanilla Agave client, meaning Agave without third-party MEV modifications such as Jito, has declined from around 6% at the start of the year to roughly 2% today. Meanwhile, adoption of <a href="https://www.helius.dev/blog/solana-mev-report#paladin"><span style="text-decoration: underline">Paladin-Agave</span></a> has risen in recent months, now accounting for about 6% of total stake.</p><h3>Network Stress Test</h3><p>On October 10th, the crypto market experienced the largest liquidation event in its history, triggering extreme volatility across all major blockchains. Despite the record-breaking surge in network activity, the Solana network and the Agave validator client demonstrated remarkable resilience and stability under pressure.</p><p></p><p>During the peak, Solana sustained six times its normal traffic levels with <a href="https://x.com/bw_solana/status/1976816940284067998"><span style="text-decoration: underline">leaders ingesting around 100,000 transaction packets per second</span></a>, while producing full blocks at the 60 million CU limit.</p><p></p><p>Even under these conditions, Solana exhibited the most stable fee dynamics of any major network while processing an order of magnitude higher throughput. True TPS (non-vote transactions) exceeded 3,200 at the height of activity.</p><p></p><p>Over the roughly two-hour peak window, Solana’s median (P50) transaction fee rose only to $0.007, less than one cent. Average fees briefly reached $0.10, and the top 1% of transactions (P99) peaked just above $1.00. This pattern demonstrates the effectiveness of <a href="https://www.helius.dev/blog/solana-local-fee-markets"><span style="text-decoration: underline">local fee markets</span></a>, which confined high fees to only those transactions interacting with contested hot accounts, while ordinary users performing simple transfers (e.g., stablecoin payments) were unaffected.</p><p></p><img src="/_next/image?url=/api/media/file/solana-transaction-fees-october-10th-2025.PNG&w=3840&q=90" alt="Solana transaction fees, October 10th 2025" /><p></p><p>For comparison, Ethereum mainnet and Arbitrum saw median fees briefly spike above $100 per transaction during the same period. Coinbase-operated L2 Base also experienced fee surges with median fees peaking at over $3. These networks lack local fee markets, applying global fee adjustments that uniformly raise costs for all users during network stress.</p><p></p><img src="/_next/image?url=/api/media/file/median-transaction-fees-oct-10th-2025.PNG&w=3840&q=90" alt="Median transaction fees, October 10th 2025" /><p></p><h3>State Growth</h3><p>Solana recently crossed a major milestone in on-chain state growth, surpassing 1 billion total accounts. Nearly <a href="https://x.com/0xWaldrobi/status/1967563514664665485"><span style="text-decoration: underline">67% of these accounts are owned by the Token Program</span></a>, of which 89.45% are associated token accounts and 10.55% token mint accounts.</p><p></p><img src="/_next/image?url=/api/media/file/number-of-accounts-on-solana-mainnet-beta.PNG&w=3840&q=90" alt="Number of accounts on Solana Mainnet-Beta" /><p></p><p>This steady expansion of state has longer-term implications for Solana clients and infrastructure providers. As the number of accounts grows, so does the demand on storage, snapshot size, and account indexing, all of which can impact performance and hardware requirements. Solutions such as <a href="https://www.helius.dev/blog/solana-builders-zk-compression"><span style="text-decoration: underline">ZK Compression</span></a> offer a promising long-term path forward for reducing state bloat.</p><h2>Agave 3.0 Release Cycle Updates</h2><h3>Cache Overhaul</h3><p>Agave 3.0 significantly reduces redundant runtime operations. A complete overhaul of the program cache eliminates hundreds of superfluous account lookups per transaction batch, resulting in approximately 30–40% faster transaction processing in internal benchmarks.</p><h3>Increase Account Limit to 40% of Block CU</h3><p>As part of the Agave 3.0 release cycle, Solana will activate <a href="https://github.com/solana-foundation/solana-improvement-documents/blob/main/proposals/0306-raise-account-cu-limits.md"><span style="text-decoration: underline">SIMD-0306: Raise Account CU Limits</span></a>. This increases the per-account CU limit from a static fixed constant of 12M to 40% of the block CU limit. Currently, each account can consume up to 12 million CUs per block. As shown in the chart below from Anza, the most heavily
