Solana Proposal Calls for Removing Block Limits After Alpenglow Upgrade
ByAinvest
Sunday, Sep 28, 2025 2:46 pm ET1min read
SOL--
The current system caps block capacity between 60 million and 100 million compute units, as mandated by SIMD-0286. This structure prevents stronger machines from processing larger blocks and creates uneven incentives for developers and operators [1]. Under the Firedancer proposal, block producers could pack as many transactions as their systems can handle. Validators unable to process these blocks in time would simply skip them, while the chain would continue without disruption [1]. This approach aligns network capacity with market demand and creates a dynamic system where throughput scales up or down based on usage rather than manual updates [1].
The proposal introduces more substantial incentives for competition. Block producers who optimize their performance could include more transactions per block, thereby earning higher rewards. In turn, slower validator clients must improve their setups to avoid falling behind and missing out on revenue [1]. Firedancer expects this to spark a "flywheel effect" in which consistent performance improvements raise the baseline capacity of the entire validator set [1].
However, not all developers are convinced about the plan. Roger Wattenhoffer, head of research at Anza, warned that removing the block limit could introduce technical risks and foster centralization [1]. Similarly, system engineer Akhilesh Singhania warned that large operators scaling into more expensive hardware could price out smaller validators [1]. These concerns highlight potential challenges in maintaining network stability and decentralization.
The proposal coincides with the pending approvals of Solana ETFs, which could drive institutional demand for SOL tokens [3]. Despite the potential benefits, the successful implementation of SIMD-0370 requires careful management to preserve network stability, which is not yet guaranteed based on the current state of the community discussion [1].
Jump Crypto's Firedancer team proposes removing Solana's block limit cap after the Alpenglow upgrade, which could incentivize validators to improve their hardware and increase network capacity. The proposal aims to create a "flywheel effect" where validators continually improve performance, leading to increased block sizes and revenue for well-capitalized block producers. However, some concerns have been raised about centralization and network stability.
Jump Crypto’s Firedancer team has introduced SIMD-0370, a proposal that could reshape how Solana processes transactions. The independent validator client wants to remove the network’s fixed compute unit (CU) block limit, arguing that validator performance should determine capacity rather than an arbitrary ceiling [1]. This proposal builds on Alpenglow, a forthcoming network upgrade that will reduce block finality from 12.8 seconds to as little as 100–150 milliseconds. Alpenglow is expected to unlock far greater efficiency for the blockchain network by reducing congestion and eliminating redundant gossip messaging [1].The current system caps block capacity between 60 million and 100 million compute units, as mandated by SIMD-0286. This structure prevents stronger machines from processing larger blocks and creates uneven incentives for developers and operators [1]. Under the Firedancer proposal, block producers could pack as many transactions as their systems can handle. Validators unable to process these blocks in time would simply skip them, while the chain would continue without disruption [1]. This approach aligns network capacity with market demand and creates a dynamic system where throughput scales up or down based on usage rather than manual updates [1].
The proposal introduces more substantial incentives for competition. Block producers who optimize their performance could include more transactions per block, thereby earning higher rewards. In turn, slower validator clients must improve their setups to avoid falling behind and missing out on revenue [1]. Firedancer expects this to spark a "flywheel effect" in which consistent performance improvements raise the baseline capacity of the entire validator set [1].
However, not all developers are convinced about the plan. Roger Wattenhoffer, head of research at Anza, warned that removing the block limit could introduce technical risks and foster centralization [1]. Similarly, system engineer Akhilesh Singhania warned that large operators scaling into more expensive hardware could price out smaller validators [1]. These concerns highlight potential challenges in maintaining network stability and decentralization.
The proposal coincides with the pending approvals of Solana ETFs, which could drive institutional demand for SOL tokens [3]. Despite the potential benefits, the successful implementation of SIMD-0370 requires careful management to preserve network stability, which is not yet guaranteed based on the current state of the community discussion [1].

Stay ahead of the market.
Get curated U.S. market news, insights and key dates delivered to your inbox.
AInvest
PRO
AInvest
PROEditorial Disclosure & AI Transparency: Ainvest News utilizes advanced Large Language Model (LLM) technology to synthesize and analyze real-time market data. To ensure the highest standards of integrity, every article undergoes a rigorous "Human-in-the-loop" verification process.
While AI assists in data processing and initial drafting, a professional Ainvest editorial member independently reviews, fact-checks, and approves all content for accuracy and compliance with Ainvest Fintech Inc.’s editorial standards. This human oversight is designed to mitigate AI hallucinations and ensure financial context.
Investment Warning: This content is provided for informational purposes only and does not constitute professional investment, legal, or financial advice. Markets involve inherent risks. Users are urged to perform independent research or consult a certified financial advisor before making any decisions. Ainvest Fintech Inc. disclaims all liability for actions taken based on this information. Found an error?Report an Issue



Comments
No comments yet