Higher

Solana

Agave

Mithril

<ul>
 <li><strong>Agave 4.2 cuts on-chain rent by roughly 90%, phased in over five steps.</strong></li>
 <li><strong>Maximum transaction size rises from 1,232 to 4,096 bytes.</strong></li>
 <li><strong>Slot times fall from 400ms to 200ms, doubling the network’s block cadence.</strong></li>
 <li><strong>The release ships Alpenglow’s full code ahead of its activation in Agave 4.3.</strong></li>
</ul>
<p>Anza, the engineering firm that maintains Solana’s main validator client, is targeting the week of August 17 for the first mainnet activations of Agave 4.2, a release that reworks how much it costs to store data on the network and how much a single transaction can carry. The update pairs a roughly 90% cut to on-chain rent with an increase in the maximum transaction size from 1,232 to 4,096 bytes and a reduction in slot times from 400 to 200 milliseconds. It also carries the full code for Alpenglow, the consensus rewrite that stays dormant until Agave 4.3, but whose presence here turns 4.2 into a staging ground for the largest protocol change Solana has attempted since launch.</p>
<h2 id="strong-rent-transaction-size-and-slot-times-all-move-at-once-strong"><strong>Rent, transaction size, and slot times all move at once</strong></h2>
<p>Anza published the 4.2 schedule on June 30 and has been running a six-week release cadence since the 4.0 cycle. The three changes are switched on one at a time: validators upgrade the software first, and each feature activates separately once enough of the network is ready. The rent reduction is the largest of the three in percentage terms.</p>
<div style="overflow-x: auto;">
 <table style="width: 100%; border-collapse: collapse; font-family: Arial,Helvetica,sans-serif; font-size: 14px; min-width: 520px;">
  <thead>
   <tr style="background: linear-gradient(90deg,#0d2b2e,#126b57); color: #ffffff;">
    <th style="padding: 12px; text-align: left; border-bottom: 2px solid #0d2b2e;">Metric</th>
    <th style="padding: 12px; text-align: center; border-bottom: 2px solid #0d2b2e;">Before</th>
    <th style="padding: 12px; text-align: center; border-bottom: 2px solid #0d2b2e;">Agave 4.2</th>
    <th style="padding: 12px; text-align: left; border-bottom: 2px solid #0d2b2e;">Goal</th>
   </tr>
  </thead>
  <tbody>
   <tr style="background: #f1f9f6;">
    <td style="padding: 11px; border-bottom: 1px solid #dcebe6;">On-chain rent <span style="color: #7c8a86; font-size: 12px;">(lamports/byte)</span></td>
    <td style="padding: 11px; text-align: center; border-bottom: 1px solid #dcebe6; color: #9aa5a2;">6,960</td>
    <td style="padding: 11px; text-align: center; border-bottom: 1px solid #dcebe6; font-weight: bold; color: #0f8a5f;">696</td>
    <td style="padding: 11px; border-bottom: 1px solid #dcebe6;">~90% cheaper state</td>
   </tr>
   <tr style="background: #ffffff;">
    <td style="padding: 11px; border-bottom: 1px solid #dcebe6;">Transaction size <span style="color: #7c8a86; font-size: 12px;">(bytes)</span></td>
    <td style="padding: 11px; text-align: center; border-bottom: 1px solid #dcebe6; color: #9aa5a2;">1,232</td>
    <td style="padding: 11px; text-align: center; border-bottom: 1px solid #dcebe6; font-weight: bold; color: #0f8a5f;">4,096</td>
    <td style="padding: 11px; border-bottom: 1px solid #dcebe6;">Atomic bundles</td>
   </tr>
   <tr style="background: #f1f9f6;">
    <td style="padding: 11px; border-bottom: 1px solid #dcebe6;">Slot time</td>
    <td style="padding: 11px; text-align: center; border-bottom: 1px solid #dcebe6; color: #9aa5a2;">400ms</td>
    <td style="padding: 11px; text-align: center; border-bottom: 1px solid #dcebe6; font-weight: bold; color: #0f8a5f;">200ms</td>
    <td style="padding: 11px; border-bottom: 1px solid #dcebe6;">2x block cadence</td>
   </tr>
   <tr style="background: #ffffff;">
    <td style="padding: 11px;">Finality <span style="color: #7c8a86; font-size: 12px;">(via 4.3)</span></td>
    <td style="padding: 11px; text-align: center; color: #9aa5a2;">12.8s</td>
    <td style="padding: 11px; text-align: center; font-weight: bold; color: #0f8a5f;">100-150ms</td>
    <td style="padding: 11px;">Sub-second settlement</td>
   </tr>
  </tbody>
 </table>
</div>
<h2 id="strong-why-a-90-rent-cut-changes-what-developers-keep-on-chain-strong"><strong>Why a 90% rent cut changes what developers keep on-chain</strong></h2>
<p>Solana charges accounts a small ongoing fee, called rent, for the data they occupy on the ledger. That fee exists to discourage inefficient use of state, since every account a program creates has to sit in the memory of every full node forever. The 4.2 target lowers the rate from 6,960 lamports per byte toward 696, a reduction the network applies gradually rather than in one jump.</p>
<p>Creating millions of user accounts or deploying programs with heavy state used to require a meaningful capital lockup, so teams designed around keeping as little as possible on-chain. Cheap state removes that upfront penalty and lets protocols hold long-lived accounts and larger data structures directly on the ledger. Storage stops being a capital decision and becomes a minor operating cost. That single change quietly rewrites years of Solana design advice.</p>
<h2 id="strong-the-1-232-byte-wall-comes-down-strong"><strong>The 1,232-byte wall comes down</strong></h2>
<p>The old ceiling was a networking artifact. Solana capped transactions at 1,232 bytes to stay inside the size of a single network packet, and after overhead that was the room left for actual data. A networking change in 2022 removed that hard constraint, which is what <strong><a href="https://github.com/solana-foundation/solana-improvement-documents/blob/main/proposals/0296-larger-transactions.md" rel="noopener noreferrer nofollow">SIMD-0296 now takes advantage of</a></strong>, delivered through the new v1 transaction format that lifts the limit to 4,096 bytes.</p>
<p>That extra room matters for anyone building complex logic. Under 1,232 bytes, developers had to split a single logical action across several transactions, which introduced rollback logic, exposure to bots that profit by reordering pending transactions, and the risk of one leg failing while another cleared. A 4,096-byte envelope lets a single transaction bundle several steps that all succeed or fail together, including zero-knowledge proofs used in private transfers, the layered approvals institutions use to authorize large transactions, and multi-step trades that previously had to be split up to fit. The v1 format also drops address lookup tables, since the full account list fits inline in most cases.</p>
<h2 id="strong-faster-slots-reward-operators-who-run-their-own-fiber-strong"><strong>Faster slots reward operators who run their own fiber</strong></h2>
<p>Cutting slot times to 200ms is the most technically demanding part of the release, delivered in five stages under SIMD-0525. Every validator now has to receive, execute, and propagate block data in half the previous window. Operators running on public internet routing rather than dedicated fiber face a higher chance of dropped slots and late votes, and that pressure tends to favor institutional setups on private backbones such as the DoubleZero fiber layer over home operators.</p>
<p>The rent cut pulls in the same direction on the hardware question. Removing 90% of the rent charge also removes the main economic brake on state bloat, and full nodes already carry the entire account set in high-performance memory that runs to hundreds of gigabytes. A cheap network to build on is not the same as a cheap network to help run.</p>
<div style="display: flex; flex-wrap: wrap; gap: 16px; font-family: Arial,Helvetica,sans-serif;">
 <div style="flex: 1 1 260px; background: #eef7f1; border-left: 4px solid #1a9d63; border-radius: 6px; padding: 16px 18px;">
  <div style="font-size: 13px; font-weight: bold; letter-spacing: 0.5px; text-transform: uppercase; color: #12784a; margin-bottom: 10px;">
   The optimistic reading
  </div>
  <ul style="margin: 0; padding-left: 18px; font-size: 14px; line-height: 1.6; color: #20302a;">
   <li>Long-lived accounts stay on-chain with no capital penalty</li>
   <li>Complex logic fits in one atomic block</li>
   <li>Settlement speed moves toward Web2 rails</li>
  </ul>
 </div>
 <div style="flex: 1 1 260px; background: #fdf4e8; border-left: 4px solid #c77d21; border-radius: 6px; padding: 16px 18px;">
  <div style="font-size: 13px; font-weight: bold; letter-spacing: 0.5px; text-transform: uppercase; color: #9c5f11; margin-bottom: 10px;">
   The cautionary reading
  </div>
  <ul style="margin: 0; padding-left: 18px; font-size: 14px; line-height: 1.6; color: #332a1f;">
   <li>Less friction against ledger bloat</li>
   <li>Higher memory and compute load per node</li>
   <li>Fiber-less operators risk dropped slots</li>
  </ul>
 </div>
</div>
<p>&nbsp;</p>
<h2 id="strong-alpenglow-is-the-real-target-and-4-2-is-the-rehearsal-strong"><strong>Alpenglow is the real target, and 4.2 is the rehearsal</strong></h2>
<p>The most consequential code in this release does nothing yet. By shipping Alpenglow in a deactivated state, Anza gives validators a live environment to test it on the community cluster before the switch flips in Agave 4.3. Alpenglow, <strong><a href="https://github.com/solana-foundation/solana-improvement-documents/blob/main/proposals/0326-alpenglow.md" rel="noopener noreferrer nofollow">defined in SIMD-0326 and approved by validators with 98% support in September 2025</a></strong>, replaces both Proof of History and TowerBFT, the two systems Solana has run since 2020.</p>
<p>The mechanism behind the speed gain is a change in how validators vote. Today they publish votes as ordinary on-chain transactions, and those votes consume around 75% of total block space, so the network spends most of its capacity confirming itself. Alpenglow’s Votor component moves voting off-chain and aggregates thousands of BLS signatures into a single compact certificate that lands on the ledger. <strong><a href="https://www.anza.xyz/blog/alpenglow-a-new-consensus-for-solana" rel="noopener noreferrer nofollow">Anza projects median finality of roughly 150ms</a></strong>, and as low as 100ms when about 80% of stake is active, against the 12.8 seconds TowerBFT needs across its 32 voting rounds. Those finality figures remain simulation-derived, and a public testnet at full validator scale may surface edge cases the community cluster did not.</p>
<h2 id="strong-the-98-3-cost-claim-and-the-fee-that-replaces-it-strong"><strong>The 98.3% cost claim and the fee that replaces it</strong></h2>
<p>The clearest economic argument for Alpenglow is what it does to validator overhead, and the headline figure needs a caveat attached.</p>
<ul>
 <li>Voting today costs a validator around 1 SOL per day, roughly $60,000 a year at recent prices.</li>
 <li>Alpenglow removes those per-slot fees and replaces them with a Validator Admission Ticket of about 0.8 SOL per day, or 1.6 SOL per epoch of roughly two days, which is burned rather than paid to anyone.</li>
 <li>IG UK calculates that net operating overhead falls by about 98.3%, from near $60,000 a year to roughly $1,000.</li>
 <li>A model from Helius, using Cogent Crypto’s profit calculator, puts the minimum profitable stake at around 450 SOL, or about $75,000, down from roughly 4,850 SOL, near $800,000.</li>
</ul>
<p>The lower barrier comes with a ceiling. The Validator Admission Ticket caps admitted validators at 2,000, so the design trades a per-slot cost for a fixed one and a membership limit rather than removing costs outright. The 4,850-to-450 SOL figure is a modelled estimate, not a guaranteed outcome, and it depends on the reward and inflation settings that ship alongside the consensus change.</p>
<h2 id="strong-what-sub-second-finality-changes-for-the-market-strong"><strong>What sub-second finality changes for the market</strong></h2>
<p>Solana currently forces developers to choose, feature by feature, how sure they need to be that a transaction is final. They can show a fast result after about 500ms and accept a small chance it later reverses, or wait roughly 12.8 seconds to be certain it can never reverse. Exchanges crediting deposits wait for the slow version. So do bridges and liquidation engines, because even a minor reversal is unacceptable. Alpenglow collapses those tiers into a single deterministic finality at 100-150ms, which is the change that makes Solana viable as a settlement layer for real-time payments, tokenized assets, and on-chain order books that clear multi-asset routes natively.</p>
<p>The full transition runs in stages from August into October 2026, and it lands while Solana pushes on client diversity through Firedancer and Mithril to reduce single points of failure. One piece is deliberately absent: Alpenglow ships without slashing, the penalty that would economically punish validators who act against the network, and community discussion has floated that only as a possible 2027 proposal. Whether the network can widen validator participation while keeping stake decentralized, without a live slashing mechanism in place, is the open question that the 4.3 activation will start to answer.</p>
<p>The post <a href="https://ethnews.com/solana-upgrade-agave-4-2-cheaper-harder/" rel="noopener noreferrer nofollow">Solana’s New Upgrade Makes It Cheaper to Use, Harder to Run</a> appeared first on <a href="https://ethnews.com" rel="noopener noreferrer nofollow">ETHNews</a>.</p>

Solana’s New Upgrade Makes It Cheaper to Use, Harder to Run

Table of Contents

ETHNews

Other articles published on Aug 2, 2026

Join our free newsletter for daily crypto updates!