736fb130-e
Solana’s 2027 roadmap targets 2x compute and 80% lower usage
Anza’s 2027 Solana roadmap targets twice the compute capacity, 80% less compute-unit use for token accounts, 96 accessible accounts and Rotor-led block distribution for validators.

Outputs
Anza’s 2027 roadmap targets double Solana’s compute capacity.
The plan seeks 80% lower compute-unit consumption for token-account transactions.
Transaction account access would rise from 64 to 96.
Rotor is slated under the 2027 roadmap to replace Turbine.
Constellation would target clearer ordering and more validator competition.
Anza’s 2027 roadmap for Solana sets two headline engineering targets: double the network’s compute capacity and cut compute-unit consumption for token-account transactions by 80%.
Brennan Watt, CEO of Solana core development team Anza, presented the technical agenda at Solana Breakpoint 2026 in London. The proposals cover transaction processing, account access, block distribution and protocol design.
These are engineering targets, not completed improvements. The presentation gives no fee estimate or exact release schedule, so the figures should be treated as development goals rather than measured network outcomes.
What does Anza plan to build?
The work falls under four pillars: Performance, Expressivity, Market Structure and Resilience. Each addresses a different operational layer, from transaction resources and account reach to block delivery and protocol complexity.
- Performance: Double compute capacity while reducing compute-unit consumption for token-account transactions by 80%.
- Expressivity: Add vector processing for models designed to run fully onchain.
- Market Structure: Build on Alpenglow with faster block distribution and a proposed replacement for Turbine.
- Resilience: Simplify the protocol and reduce special cases so future changes can be made more safely.
The four pillars touch different stages of the same transaction path. Account limits and direct reads affect transaction composition. Rotor and Constellation affect block delivery and ordering. Resilience covers the protocol’s ability to absorb later changes.
Performance pairs the capacity increase with lower compute consumption for token-account transactions. Anza wants more network headroom and lower resource use for these operations, although the presentation does not translate that goal into fees or costs.
Expressivity adds vector processing for models that run fully onchain. It also raises the number of accounts a transaction can access from 64 to 96, widening the transaction’s account scope.
Anza would have transactions read account data directly instead of copying it. That should reduce the amount of data moved for each transaction, while the larger account limit gives one transaction access to more state.
Market Structure work builds on Alpenglow with faster block distribution. Anza is developing Rotor to replace Turbine, Solana’s existing block propagation mechanism, and to improve how blocks spread through the network.
The same pillar introduces Constellation, which aims to make ordering rules clearer and increase competition among validators. Planned elements include ordering within the protocol, support for multiple proposers, geographically aware leader rotations and transaction concurrency.
These proposals reach validator operations, not just application transactions. Multiple proposers and geographically aware leader rotations would alter block-production roles, while transaction concurrency allows overlapping transaction progress.
Resilience focuses on simplifying the protocol. Anza’s stated approach is to reduce special cases, with the aim of making future changes safer.
What does this change for users and validators?
For users, the practical proposal is more efficient token-account work and a wider account window. If Anza reaches its goals, compute consumption falls 80%, a transaction can access 96 accounts, and account data is read without the planned copying step. The agenda does not convert those gains into a fee promise.
For validators and proposers, the changes are more structural. Rotor would replace the propagation layer, while Constellation would alter ordering, proposer participation and leader selection. The intended result is faster block spread and more competition among validators.
Anza presented proposed engineering work, not deployed upgrades. The roadmap supplied no benchmark for its capacity, efficiency or distribution targets, leaving those claims open to measurement once the code ships.
The next checkpoint is 2027 development work. Until releases and measurements arrive, the 2x capacity, 80% savings and 96-account limit remain roadmap targets rather than operating facts.
via en.cryptonomist.ch (Source)
More from Marcus Bennett
Show full bio
Senior reporter covering money, funding and market shifts around crypto and web3 industry at Mempool Brief.
1,512 articles