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

The Channel Factories We’ve Been Waiting For

The Channel Factories We’ve Been Waiting For

The post The Channel Factories We’ve Been Waiting For appeared on BitcoinEthereumNews.com. Visions of future technology are often prescient about the broad strokes while flubbing the details. The tablets in “2001: A Space Odyssey” do indeed look like iPads, but you never see the astronauts paying for subscriptions or wasting hours on Candy Crush.  Channel factories are one vision that arose early in the history of the Lightning Network to address some challenges that Lightning has faced from the beginning. Despite having grown to become Bitcoin’s most successful layer-2 scaling solution, with instant and low-fee payments, Lightning’s scale is limited by its reliance on payment channels. Although Lightning shifts most transactions off-chain, each payment channel still requires an on-chain transaction to open and (usually) another to close. As adoption grows, pressure on the blockchain grows with it. The need for a more scalable approach to managing channels is clear. Channel factories were supposed to meet this need, but where are they? In 2025, subnetworks are emerging that revive the impetus of channel factories with some new details that vastly increase their potential. They are natively interoperable with Lightning and achieve greater scale by allowing a group of participants to open a shared multisig UTXO and create multiple bilateral channels, which reduces the number of on-chain transactions and improves capital efficiency. Achieving greater scale by reducing complexity, Ark and Spark perform the same function as traditional channel factories with new designs and additional capabilities based on shared UTXOs.  Channel Factories 101 Channel factories have been around since the inception of Lightning. A factory is a multiparty contract where multiple users (not just two, as in a Dryja-Poon channel) cooperatively lock funds in a single multisig UTXO. They can open, close and update channels off-chain without updating the blockchain for each operation. Only when participants leave or the factory dissolves is an on-chain transaction…
Share
BitcoinEthereumNews2025/09/18 00:09
Share