Solana Changelog: Tiered Account Storage, Debugging Programs, and Anchor Updates

In the ever-evolving world of blockchain technology, Solana continues to push the boundaries of innovation and performance. This week's changelog brings exciting updates and proposals that further solidify Solana's position as a leading blockchain platform. From tiered account storage to improved debugging capabilities and significant Anchor updates, there's a lot to unpack. Let's dive into the details of these developments and what they mean for the Solana ecosystem.

Grizzly Thawn Submissions Now Open

The Solana Foundation has announced that submissions for Grizzly Thawn are now open. This presents an excellent opportunity for developers and project teams to showcase their innovative work on the Solana blockchain. To assist participants in refining their submissions, the Solana Foundation's developer relations team will be hosting office hours. This initiative demonstrates Solana's commitment to fostering a vibrant and supportive ecosystem for developers.

Core Community Call: Shaping Solana's Future

The Core Community Call, scheduled for Friday at 1900 UTC, is a crucial event for the Solana ecosystem. This call brings together core contributors from various teams, including Solana Labs, Fire Dancers, Mango, Jito, and others. The purpose of this call is to discuss and align on potential changes and features for the Solana network. While the final decisions on network changes ultimately rest with the validators, these discussions play a vital role in shaping the direction of Solana's development.

Tiered Account Storage: Optimizing Validator Performance

One of the most intriguing proposals discussed in this changelog is the concept of tiered account storage. This proposal, specific to the Solana Labs client, aims to optimize how accounts are stored on validator nodes based on their usage frequency. The proposal introduces a distinction between "hot" and "cold" accounts:

• Hot accounts: Frequently accessed accounts
• Cold accounts: Rarely used accounts

The tiered storage system proposes storing hot accounts in RAM for quick access, while cold accounts would be stored on disk. This approach mimics traditional caching strategies used in computer systems and databases. By implementing this tiered storage system, Solana aims to improve overall validator performance and resource utilization.

Compressed NFTs: A Game-Changer for Digital Collectibles

Jonas highlighted an exciting development in the Solana ecosystem: compressed NFTs. This new approach to handling Non-Fungible Tokens (NFTs) on Solana promises to dramatically reduce costs and increase scalability. Nick from Helius has created an end-to-end example demonstrating the power of compressed NFTs.

Compressed NFTs work by storing only a proof of the NFT data on-chain, while the full metadata is cached by validators. This innovative approach offers several advantages:

1. Reduced on-chain storage requirements
2. Significantly lower minting costs
3. Ability to create massive collections at scale

Jonas mentioned that with compressed NFTs, it's possible to mint approximately one million NFTs for just 5 SOL, which is a game-changing reduction in cost compared to traditional NFT minting on other blockchains.

The example provided by Helius includes the entire process of creating a collection, minting an NFT, transferring it, and even attempting to redeem it. This comprehensive demonstration showcases the potential of compressed NFTs and sets the stage for new possibilities in the world of digital collectibles on Solana.

Expanding Transaction Capabilities: New Compute Budget Instruction

A significant update to Solana's transaction processing capabilities was introduced with a new compute budget instruction. This instruction allows developers to request changes to the loaded account size limits within a transaction. The current limit for data that can be loaded in a single transaction is 64 megabytes, a substantial increase from the previous 10-megabyte limit.

This new instruction offers two primary benefits:

1. Requesting higher limits: Developers can request a higher limit by paying more in compute units or potentially fees in the future.
2. Requesting lower limits: For transactions that don't require as much data, developers can request a lower limit, potentially reducing compute usage and associated costs.

While the pricing model for these limit adjustments is still being finalized, it's likely to be implemented through a future SIMD (Single Instruction, Multiple Data) update. This flexibility in transaction data limits opens up new possibilities for complex on-chain operations and further enhances Solana's scalability.

Anchor: A Major Update for Solana Developers

One of the most exciting announcements in this changelog is the significant update to Anchor, a popular development framework for Solana. Jonas expressed enthusiasm about the continued development of Anchor, which now boasts 78 contributors. The latest release introduces several new features and improvements that will greatly benefit Solana developers:

1. IDL Account Management:

   • Ability to close IDL accounts
   • Support for very large IDL accounts

2. Token Operations:

   • Introduction of transfer_checked and approve_checked functions

3. Account Interfaces:

   • New interfaces for managing multiple token accounts, which is particularly useful with the introduction of Token 2022

4. Transaction Support:

   • Added support for version transactions

5. Bytecode Loader:

   • Support for the new Solana Program Format (SPF) bytecode loader

These updates to Anchor demonstrate the ongoing commitment to improving the developer experience on Solana. The introduction of account interfaces for managing multiple token accounts is particularly noteworthy, as it paves the way for easier integration with Token 2022, which offers advanced features for token management on Solana.

Debugging Solana Programs: A Step Towards Easier Development

Another significant development highlighted in the changelog is the introduction of documentation for debugging on-chain code. While the current process isn't yet fully streamlined, it represents a crucial step forward in making Solana development more accessible and efficient.

The debugging process involves:

1. Installing the Code LLDB extension for Visual Studio Code
2. Pointing to the LBP LLDB SO library
3. Setting up task.json and launch.json files

While this method has some limitations, such as the inability to use Cross-Program Invocations (CPIs) or access on-chain data during debugging, it provides a solid foundation for future improvements. The availability of this documentation opens the door for the community to build upon these efforts and potentially create more user-friendly debugging tools.

Jonas and Jacob discussed the potential for bundling these debugging steps into a single VS Code extension, which would significantly simplify the process for developers. They also mentioned the exciting possibility of integrating this debugging functionality into Solana Playground, a web-based development environment for Solana. Such integrations could dramatically reduce the barriers to entry for new Solana developers and improve productivity for experienced ones.

Cluster Performance Improvements: Reducing Shreds Per Slot

The changelog also highlighted ongoing efforts to optimize Solana's cluster performance. A series of commits have focused on reducing the number of shreds per slot on the cluster. Shreds are the smallest units of data transferred between validators that make up a block.

The improvements have resulted in a dramatic reduction in shreds per slot:

• Previous: 557,000 shreds per slot
• Current: 32,000 shreds per slot

This significant reduction in shreds per slot offers several benefits:

1. Improved cluster performance
2. Enhanced ability to handle large amounts of transactional data
3. Reduced network overhead between validators

These optimizations contribute to Solana's ongoing efforts to maintain its position as one of the fastest and most scalable blockchain networks in the industry.

The Road Ahead: Grizzly Thawn and Community Engagement

As the changelog discussion wrapped up, both Jonas and Jacob expressed excitement about the upcoming Grizzly Thawn submissions. This event promises to showcase the creativity and innovation within the Solana developer community. The enthusiasm from the hosts reflects the broader sentiment within the Solana ecosystem – a sense of anticipation for the new projects and ideas that will emerge from this initiative.

The mention of potentially reviewing thousands of submissions underscores the scale and vibrancy of the Solana developer community. It's a testament to the platform's growing popularity and the diverse range of applications being built on Solana.

Conclusion: Solana's Continuous Evolution

This changelog episode highlights Solana's commitment to continuous improvement and innovation. From low-level optimizations like tiered account storage and shred reduction to developer-facing tools like improved debugging capabilities and Anchor updates, Solana is evolving on multiple fronts.

The introduction of compressed NFTs showcases Solana's ability to innovate in the application layer, potentially revolutionizing the NFT space with dramatically reduced costs and increased scalability. Meanwhile, the ongoing community engagement through events like Grizzly Thawn and the Core Community Call demonstrates Solana's dedication to fostering a collaborative and vibrant ecosystem.

As Solana continues to push the boundaries of blockchain technology, these updates and improvements pave the way for more efficient, scalable, and developer-friendly blockchain applications. The future looks bright for Solana, and we can expect to see even more exciting developments in the coming weeks and months.

Facts + Figures

• Grizzly Thawn submissions are now open for Solana developers to showcase their projects.
• The Core Community Call is scheduled for Friday at 1900 UTC, bringing together core contributors to discuss potential network changes.
• A new tiered account storage proposal aims to optimize validator performance by storing hot accounts in RAM and cold accounts on disk.
• Compressed NFTs on Solana allow minting of approximately one million NFTs for just 5 SOL.
• The loaded account size limit for Solana transactions has been increased from 10 megabytes to 64 megabytes.
• A new compute budget instruction allows developers to request changes to the loaded account size limits within a transaction.
• Anchor, a popular Solana development framework, now has 78 contributors and received a major update with new features.
• New debugging documentation for on-chain Solana programs has been released, using the Code LLDB extension for Visual Studio Code.
• Cluster performance improvements have reduced the number of shreds per slot from 557,000 to 32,000.
• The Solana Program Format (SPF) is a new bytecode loader that improves upon the previous BPF format.

Questions Answered

What is the Grizzly Thawn event?

Grizzly Thawn is a submission-based event for Solana developers to showcase their projects. The Solana Foundation has opened submissions for this event, allowing developers to present their innovative work on the Solana blockchain. To support participants, the Solana Foundation's developer relations team is offering office hours to provide feedback and help refine submissions.

How does the proposed tiered account storage work?

The proposed tiered account storage system aims to optimize validator performance by storing accounts differently based on their usage frequency. Hot accounts, which are frequently accessed, would be stored in RAM for quick access. Cold accounts, which are rarely used, would be stored on disk. This approach mimics traditional caching strategies and is designed to improve overall validator performance and resource utilization on the Solana network.

What are compressed NFTs on Solana?

Compressed NFTs are a new approach to handling Non-Fungible Tokens on Solana that dramatically reduces costs and increases scalability. Instead of storing all NFT metadata on-chain, compressed NFTs store only a proof of the data on-chain while the full metadata is cached by validators. This method allows for the minting of approximately one million NFTs for just 5 SOL, significantly reducing the cost compared to traditional NFT minting on other blockchains.

What major updates were introduced in the latest Anchor release?

The latest Anchor release introduced several significant features and improvements:

1. The ability to close IDL accounts and support for very large IDL accounts
2. New token operations like transfer_checked and approve_checked
3. Interfaces for managing multiple token accounts, particularly useful with Token 2022
4. Support for version transactions
5. Compatibility with the new Solana Program Format (SPF) bytecode loader

These updates aim to enhance the developer experience and expand the capabilities of applications built on Solana.

How has Solana improved its cluster performance?

Solana has improved its cluster performance by reducing the number of shreds per slot. Shreds are the smallest units of data transferred between validators that make up a block. Recent optimizations have reduced the number of shreds per slot from 557,000 to 32,000. This significant reduction improves overall cluster performance, enhances the ability to handle large amounts of transactional data, and reduces network overhead between validators.

What is the new compute budget instruction for Solana transactions?

The new compute budget instruction allows developers to request changes to the loaded account size limits within a transaction. With this instruction, developers can request higher limits by paying more in compute units (or potentially fees in the future), or lower limits for transactions that don't require as much data, potentially reducing compute usage and costs. This flexibility in transaction data limits opens up new possibilities for complex on-chain operations and further enhances Solana's scalability.

How can developers debug Solana programs?

Solana has introduced documentation for debugging on-chain code. The process involves installing the Code LLDB extension for Visual Studio Code, pointing to the LBP LLDB SO library, and setting up task.json and launch.json files. While this method has some limitations, such as the inability to use Cross-Program Invocations (CPIs) or access on-chain data during debugging, it provides a foundation for future improvements in Solana program debugging.

What is the Core Community Call?

The Core Community Call is a regular meeting between core contributors of the Solana protocol, including teams from Solana Labs, Fire Dancers, Mango, Jito, and other key players in the ecosystem. Held on Fridays at 1900 UTC, this call serves as a forum to discuss potential changes and features for the Solana network. While the final decisions on network changes are made by validators, these discussions play a crucial role in shaping the direction of Solana's development.