PANews reported on September 29th that according to The Block, Jump Crypto's Firedancer team is building a high-performance client for Solana. Their SIMD-0370 proposal proposes removing the current fixed limit of 60 million CUs per block (a previous proposal had raised this limit to 100 million) after Solana's major Alpenglow upgrade, scheduled for testing later this year. Without a fixed limit, block size would adjust based on the transaction volume accommodated by high-performance validators, while weaker validators would automatically abstain from voting on oversized blocks by skipping the voting mechanism. The proposal argues that removing the limit would encourage well-funded block producers to upgrade their hardware and add more transactions to increase revenue, incentivizing others to follow suit, creating a "flywheel effect" and increasing the average capacity of validator clients. Roger Wattenhofer, head of research at Anza and a driving force behind Solana's Alpenglow upgrade, supports removing the limit but also expresses concerns about potential centralization and network stability risks. He stated that these issues are solvable and that he has been a staunch supporter of removing the limit.PANews reported on September 29th that according to The Block, Jump Crypto's Firedancer team is building a high-performance client for Solana. Their SIMD-0370 proposal proposes removing the current fixed limit of 60 million CUs per block (a previous proposal had raised this limit to 100 million) after Solana's major Alpenglow upgrade, scheduled for testing later this year. Without a fixed limit, block size would adjust based on the transaction volume accommodated by high-performance validators, while weaker validators would automatically abstain from voting on oversized blocks by skipping the voting mechanism. The proposal argues that removing the limit would encourage well-funded block producers to upgrade their hardware and add more transactions to increase revenue, incentivizing others to follow suit, creating a "flywheel effect" and increasing the average capacity of validator clients. Roger Wattenhofer, head of research at Anza and a driving force behind Solana's Alpenglow upgrade, supports removing the limit but also expresses concerns about potential centralization and network stability risks. He stated that these issues are solvable and that he has been a staunch supporter of removing the limit.

Jump’s Firedancer Team Proposes Removing Solana Block Limit After Alpenglow Upgrade

2025/09/29 07:16

PANews reported on September 29th that according to The Block, Jump Crypto's Firedancer team is building a high-performance client for Solana. Their SIMD-0370 proposal proposes removing the current fixed limit of 60 million CUs per block (a previous proposal had raised this limit to 100 million) after Solana's major Alpenglow upgrade, scheduled for testing later this year. Without a fixed limit, block size would adjust based on the transaction volume accommodated by high-performance validators, while weaker validators would automatically abstain from voting on oversized blocks by skipping the voting mechanism. The proposal argues that removing the limit would encourage well-funded block producers to upgrade their hardware and add more transactions to increase revenue, incentivizing others to follow suit, creating a "flywheel effect" and increasing the average capacity of validator clients. Roger Wattenhofer, head of research at Anza and a driving force behind Solana's Alpenglow upgrade, supports removing the limit but also expresses concerns about potential centralization and network stability risks. He stated that these issues are solvable and that he has been a staunch supporter of removing the limit.

Disclaimer: The articles reposted on this site are sourced from public platforms and are provided for informational purposes only. They do not necessarily reflect the views of MEXC. All rights remain with the original authors. If you believe any content infringes on third-party rights, please contact service@support.mexc.com for removal. MEXC makes no guarantees regarding the accuracy, completeness, or timeliness of the content and is not responsible for any actions taken based on the information provided. The content does not constitute financial, legal, or other professional advice, nor should it be considered a recommendation or endorsement by MEXC.
Share Insights

You May Also Like