Solana Changelog: Blockstore Updates, Breakpoint Highlights, and Transaction Constraint Relaxation

In the latest episode of the Solana Changelog, hosts Nick and Jacob from the Solana Foundation DevRel team dive into recent developments in the Solana ecosystem. From exciting highlights of the Breakpoint conference to significant updates in the blockchain's codebase, this episode provides valuable insights for developers and enthusiasts alike.

Breakpoint Conference Highlights

The Solana Breakpoint conference, which recently concluded, was a hotbed of innovation and exciting announcements. The hosts shared their favorite moments and key takeaways from the event.

Web3.js Presentation

One of the standout presentations at Breakpoint was delivered by Stephen Luscher, focusing on the new Web3.js. Nick praised Luscher's presentation skills and the content of the talk, highlighting the significance of this update for the Solana developer community.

Runtime V2 Unveiling

Perhaps the most anticipated presentation at Breakpoint was the unveiling of Runtime V2 by Alexander and Alessandro. Jacob noted:

"Runtime V2 is a very exciting thing. I believe they're trying to get it out sometime next year. I think it's like early next year in testnet is their plan."

The crowd's reaction to this presentation was overwhelmingly positive, with Nick mentioning that it received the most enthusiastic ovation from the audience. This new runtime is expected to revolutionize development on Solana, improving the developer experience significantly.

Firedancer on Testnet

Another highlight was the presentation on Firedancer, Solana's new validator client, now running on testnet. Jacob shared an interesting tidbit:

"The patch version was 11.04, which is kind of hilarious because if you think of if you have 1,104 patch versions, if we were having that many deployments of like the normal Solana, I think everybody would be really angry on the validators."

This high version number indicates the rapid development and iteration happening with Firedancer, showcasing Solana's commitment to improving its infrastructure.

SHA-256 Optimization

Kevin Bauer's presentation on optimizing SHA-256 caught Jacob's attention. The optimization is expected to have far-reaching implications, potentially benefiting not just Solana but the broader cryptographic community.

FPGA Performance Breakthrough

A particularly impressive demonstration involved running Signify on FPGAs:

"They ran, I think, Signify on FPGAs. And then something like 8 million TPS on a seven-year-old FPGA wild."

This incredible performance on older hardware underscores the potential for massive scalability improvements in the Solana ecosystem.

Accessing Breakpoint Content

For those who couldn't attend Breakpoint in person, Nick highlighted the availability of all presentations on the Solana YouTube channel. This resource allows the entire community to benefit from the wealth of knowledge shared at the conference.

Recent Commits and Updates

The hosts then shifted focus to recent commits in the Solana codebase, highlighting two significant updates.

Blockstore Improvement

The first commit, by developer Trent (GitHub username Chrysler Carrots), addresses an issue with the blockstore:

"This one will only return blocks on root slots. So what does that mean? In the previous version, what happened was we were returning blocks that were for unroot slots from the block store, and that would cause issues like you would get back the block and then it would get flushed because it was not actually rooted."

This update ensures that only rooted blocks are returned from RPC methods like get_block_time and get_block, improving consistency and reliability for developers interacting with the Solana blockchain.

Fee Burning Mechanism

The second commit, by developer Starry, introduces a mechanism for burning fees collected into invalid accounts:

"You can actually see that there's a associated SIMD with it. And what it does is based off of the fee distribution, every epoch, you could have distributed fees to non-system and accounts. This will basically just make it impossible to do that."

This change enhances the security and integrity of Solana's fee distribution system, preventing potential exploits or unintended fee allocations.

Web3.js Update and Community Involvement

The hosts emphasized the importance of the new Web3.js version, encouraging developers to try it out and provide feedback.

How to Access the New Web3.js

Nick explained how developers can start using the new version:

"You can install it directly from NPM. You can see it here on the screen, the @TP tag, or you can go to this URL and actually, you know, view some of the information with it."

Community Feedback Opportunity

Both hosts stressed the unique opportunity for the community to shape the future of Web3.js:

"This is the entire community's chance to give their input on what they want it to look like. Steven Luscher and the rest of the Solana Labs team that's working on this, they're very receptive to that type of feedback."

Direct Support from Solana Labs

For developers looking to upgrade their dApps to the new Web3.js, Jacob highlighted an exciting opportunity:

"If you're actually upgrading your dApp from the previous one to the new one, their team will actually help you because they want to find all the bugs early."

This direct support from the Solana Labs team is an unprecedented opportunity for developers to get expert assistance in adopting the new Web3.js, all free of charge.

SIMD of the Week: Relaxed Transaction Constraints

The hosts introduced SIMD 82, a proposal to relax certain transaction constraints in Solana.

Purpose of Constraint Relaxation

Nick explained the rationale behind this proposal:

"This is a proposal to relax some of the constraints or like the current checks that a transaction goes through before it gets added to a block. Right now there's a bunch of checks. A lot of them are very, very necessary, like you would assume, but some of those checks are actually somewhat unnecessary."

Future Implications

Jacob elaborated on the long-term goals of this change:

"It's all for a future work of asynchronous execution. So you can have basically multiple block executors or asynchronous program execution. There's a APEX is what the SIMD is called. It's all for that much larger project, making sure we can do asynchronous execution and block producing."

This change is part of a broader strategy to enhance Solana's scalability and performance through asynchronous execution capabilities.

Additional Resources

For those interested in diving deeper into the technical aspects of this proposal, Jacob mentioned:

"Andrew who wrote this SIMD has full information written out on his blog of explaining the two, he actually made a couple of SIMDs, including this one of how these fit together overall and what to expect on like how they work together, how they actually allow asynchronous execution in the future and more."

Important PSA: Compute Budget Instruction Deprecation

The hosts concluded with an important public service announcement regarding the deprecation of an old compute budget instruction.

What's Being Deprecated

Jacob explained:

"There is a feature that is going to be activated in the near future. It's currently, I think it's like the fifth one or so on the feature gate list. This is to remove or deprecate, fully deprecate the currently deprecated request units compute budget instruction."

Impact on Developers

This change will affect about 2% of transactions on mainnet. Jacob warned:

"Once it's gone, your transactions will fail. So upgrade to the newest, you can find the information on how to use the newest or how to request units on the compute budget program on solana cookbook.com."

Where to Find Updated Information

Developers can find updated information on how to use the new compute budget instructions on the Solana Cookbook website and in the official Solana documentation under the compute budget section.

Conclusion

This episode of the Solana Changelog provided a comprehensive overview of recent developments in the Solana ecosystem. From the exciting announcements at Breakpoint to critical updates in the blockchain's codebase and developer tools, the Solana community continues to demonstrate its commitment to innovation and improvement.

The highlights from Breakpoint, including the unveiling of Runtime V2 and the impressive performance demonstrations, showcase Solana's position at the forefront of blockchain technology. The ongoing development of Web3.js and the opportunity for community involvement in its evolution underline Solana's commitment to creating a robust and user-friendly developer ecosystem.

The updates to the blockstore and fee burning mechanism demonstrate Solana's attention to detail in improving the blockchain's core functionality. Meanwhile, the proposal to relax transaction constraints points towards future enhancements in scalability and performance through asynchronous execution.

As Solana continues to evolve, developers and users alike can look forward to improved performance, enhanced developer tools, and exciting new capabilities. The Solana Changelog remains an invaluable resource for staying up-to-date with these rapid developments in the Solana ecosystem.

Facts + Figures

• Breakpoint conference recently concluded with several key presentations and announcements
• Stephen Luscher presented on the new Web3.js, which is now available for developers to try
• Runtime V2 was unveiled at Breakpoint, with plans for testnet release in early 2024
• Firedancer, Solana's new validator client, is running on testnet with version 11.04
• A demonstration showed 8 million TPS running on a seven-year-old FPGA
• A recent commit ensures that only rooted blocks are returned from RPC methods like get_block_time and get_block
• Another commit introduces a mechanism for burning fees collected into invalid accounts
• SIMD 82 proposes to relax certain transaction constraints to enable future asynchronous execution
• About 2% of transactions on Solana mainnet are still using the deprecated request units compute budget instruction
• The Solana Labs team is offering free support to developers upgrading their dApps to the new Web3.js
• All Breakpoint presentations are available on the Solana YouTube channel
• The compute budget instruction deprecation is currently fifth on the feature gate list for activation

Questions Answered

What were the main highlights from the Solana Breakpoint conference?

The main highlights from Solana Breakpoint included Stephen Luscher's presentation on the new Web3.js, the unveiling of Runtime V2, demonstrations of Firedancer on testnet, and impressive performance showcases like 8 million TPS on a seven-year-old FPGA. These presentations highlighted Solana's ongoing development and potential for massive scalability improvements in the near future.

How can developers start using the new version of Web3.js?

Developers can start using the new version of Web3.js by installing it directly from NPM using the @TP tag. The Solana team is encouraging developers to try out the new version, build something with it, and provide feedback on their experience. Additionally, the Solana Labs team is offering direct support to developers who are upgrading their dApps from the previous version to the new one, providing a unique opportunity for hands-on assistance.

What is SIMD 82 and why is it important?

SIMD 82 is a proposal to relax certain transaction constraints in Solana. It's important because it lays the groundwork for future asynchronous execution capabilities, which could significantly enhance Solana's scalability and performance. The proposal aims to remove unnecessary checks while maintaining essential constraints, potentially enabling multiple block executors and asynchronous program execution in the future.

What changes are coming to the compute budget instruction in Solana?

An important change is coming to the compute budget instruction in Solana. The currently deprecated request units compute budget instruction will be fully removed in the near future. This will affect about 2% of transactions on mainnet, and once removed, transactions using the old instruction will fail. Developers are advised to upgrade to the newest version of the compute budget instruction, with information available on the Solana Cookbook website and in the official documentation.

How has the blockstore been improved in recent commits?

A recent commit has improved the blockstore by ensuring that only rooted blocks are returned from RPC methods like get_block_time and get_block. Previously, blocks from unrooted slots could be returned, causing issues where blocks might be flushed before they were actually rooted. This update improves consistency and reliability for developers interacting with the Solana blockchain.

What is Firedancer and what's its current status?

Firedancer is Solana's new validator client. It's currently running on testnet with version 11.04, which indicates rapid development and iteration. The high version number (11.04) suggests numerous improvements and updates have been made to Firedancer as it's being prepared for wider deployment.

How is Solana improving its fee distribution system?

Solana is improving its fee distribution system through a recent commit that introduces a mechanism for burning fees collected into invalid accounts. This change enhances the security and integrity of the fee distribution process by preventing the distribution of fees to non-system accounts, thereby closing potential loopholes or unintended fee allocations.

What resources are available for developers who couldn't attend Breakpoint?

For developers who couldn't attend Breakpoint in person, all presentations from the conference are available on the Solana YouTube channel. This allows the entire community to benefit from the wealth of knowledge shared at the event, including talks on Web3.js, Runtime V2, Firedancer, and various performance optimizations.