Solana Change Log: SIMD Updates, Program Deployments, and Web3.js v2

In the latest episode of the Solana Change Log, Nick from the Solana Foundation DevRel team and Jonas delve into the recent developments and improvements in the Solana ecosystem. This comprehensive update covers a range of topics, from SIMD updates to program deployments and the eagerly anticipated release of Web3.js v2. Let's explore these exciting changes and their implications for the Solana network.

Top Projects

Lulo

Score: 7,586.13

Bonk

Score: 4,806.12

Sphere

Score: 2,544.42

Moonwalk

Score: 2,026.11

SIMD191: Relaxing Transaction Constraints

The episode kicks off with a discussion of SIMD191, a proposal to relax transaction constraints, specifically for loading failures. This improvement, proposed by Andrew Fitzgerald from ANZA, is actually a part of a larger initiative, splitting a previous SIMD (believed to be SIMD83) into more manageable, bite-sized chunks.

The primary focus of SIMD191 is on handling loading failures more efficiently. Currently, when transactions are processed, they may fail due to various constraints before being included in a block. This means that validators are performing computations and expending resources without being able to collect transaction fees for their efforts.

By relaxing some of these constraints, SIMD191 aims to allow these transactions to fail and still be included in a block. This change would enable validators to collect fees for the processing they've already performed, rather than wasting compute resources without compensation.

Jonas emphasizes the importance of this change, stating:

"I think it's a great idea that the validators get paid for what they are actually processing. Otherwise, you can just send them tons of stuff and deduce them, basically. So I think it's a very good change."

This improvement not only ensures fair compensation for validators but also contributes to the overall efficiency and sustainability of the Solana network.

Improving Program Deployments

One of the significant updates discussed in the episode relates to enhancing the program deployment process on Solana. Jonas, referred to as "Woody4618" in the discussion, highlights the ongoing efforts to "make program deploys great again."

The current challenges in program deployment stem from issues with stake connections, particularly when using tools like Helios and Triton. Jonas explains that many transactions, especially when not using the "skip pre-flight check" option, aren't getting stake-weighted properly.

To address this, the Solana CLI, starting from version 2.2 of Agar, will introduce the ability to define the skip pre-flight check. This enhancement is expected to significantly simplify the process of landing transactions, particularly for program deployments.

Jonas provides a detailed explanation of the current workaround and the upcoming improvements:

"And in the meantime, what you need to do is you need to look at the current fees. So you can, for example, use the gas tracker by quick note or try to figure them out yourself or use an API of one of the RPC providers. And then if you have a non-stake note, what you need to do is you need to set compute units as, I would say, a bit a little bit above the low. And then you can set the max sign attempts to 1000 or something. And then you can just let it run."

For users with staked nodes or those paying for dedicated nodes, Jonas suggests using the "--use-rpc-for-write" option, which can significantly speed up program deployment to just a few seconds.

Additionally, Jonas mentions a useful tip for developers facing deployment issues:

"And if anything fails, I don't know if everyone knows, but you can just do Solana program show buffers, then it shows you the buffers, and you can close them again so that you get your SOL back in case you have an error."

These improvements and workarounds demonstrate Solana's commitment to enhancing the developer experience and streamlining the deployment process.

Lifting CPI Call Restrictions

Another significant update discussed in the episode is the implementation of a feature gate to lift certain Cross-Program Invocation (CPI) call restrictions. This change, stemming from SIMD163, aims to improve the efficiency of CPI calls within the Solana ecosystem.

Nick explains the implications of this update:

"Basically what this is doing is it relaxes, it removes one of the CPI checks that it has to make it so when you're actually performing CPI, those CPI calls can actually be more efficient because it removes one of the checks and it makes it so data doesn't have to be double deserialized and double handled."

By removing one of the checks during CPI calls, this update reduces the amount of data processing required, leading to more efficient transactions. This improvement is particularly significant as it affects all transactions that involve CPI, potentially leading to a notable performance boost across the network.

Doubling Program Cache Size

In line with Solana's ongoing efforts to enhance performance, the episode highlights a straightforward yet impactful change: doubling the program cache size for validators. Nick explains the simplicity and effectiveness of this update:

"Basically he just doubled, it's actually a very straightforward PR. He doubled the program cache size, making it so the total program cache that the validators will actually have stored within their RAM, just doubles the size."

This increase in cache size has several benefits:

1. Reduced frequency of automatic program eviction from the cache
2. Ability to store more data for longer periods
3. Improved overall performance for validators

Jonas adds context to why this change is significant:

"Yeah, so it looks like many of the programs were not actually cached because the cache was too small, right? So then the next transactions come in, it loads the next program and then it's not in the cache anymore, it's the same program is called again."

By addressing this limitation, Solana is taking another step towards optimizing its infrastructure and improving transaction processing efficiency.

Executable Flag Optimization

The podcast touches upon an ongoing initiative to optimize the use of the "executable" flag within the Solana runtime. This update involves removing the is_executable flag checks and instead relying on the owner check to determine if an account is executable (i.e., a program account).

Nick explains the rationale behind this change:

"Basically the runtime has been updated to instead of having this Boolean value stored within each of the accounts, whether it's executable or not, AKA a program account or not. They're actually just using the owner check instead because anything that's executable has to be owned by the loader program, one of the loader programs."

This optimization eliminates the need to store a binary value in every account on Solana, potentially leading to reduced storage requirements and improved efficiency in account handling.

Web3.js Version 2 Release

One of the most exciting announcements in this episode is the imminent release of Web3.js version 2. This new version of the popular JavaScript library for interacting with the Solana blockchain brings several improvements and changes.

Jonas highlights the significance of this release:

"So we have the new Web3.js is coming. We talked about it a little bit last week already, but now it's actually coming. So it will soon be, how's it called? Not release candidate anymore, but version two."

The hosts encourage developers to try out the new version, which can be accessed using the @2 tag instead of @rc. They emphasize that while the new version is faster and smaller, it also introduces some changes that developers should be aware of.

To assist developers in transitioning to the new version, the Solana cookbook has been updated with a new feature:

"So in the cookbook, now we have these cool tabs here. So we can actually have different versions. So we can have Web3.js v2 and v1."

This side-by-side comparison of v1 and v2 code snippets will be invaluable for developers looking to update their projects or learn the new syntax.

V-Logs: Efficient Solana Data Streaming

The episode briefly touches on V-Logs, described as a "fast lightweight client for streaming Solana data." This tool promises to reduce infrastructure costs by up to 50%, although the hosts mention they haven't personally tested it yet.

Nick expands on the potential impact of V-Logs:

"One of the things that they're shooting for is making it so people can run their own indexers and like index anything on Solana with just less infrastructure costs, you don't have to run like a full node or a full RPC in order to do it, which is really, really cool."

This development could significantly lower the barrier to entry for developers and projects looking to build on Solana, as it reduces the infrastructure requirements for data indexing and analysis.

Stack Exchange Champions

The episode concludes with a shoutout to the top contributors on the Solana Stack Exchange. This recognition highlights the community's active involvement in supporting and educating fellow developers.

Jonas emphasizes the importance of this community-driven support:

"So whenever we answer a question helps everybody. So it's really cool that everyone is helping here."

This section of the podcast underscores the collaborative nature of the Solana ecosystem and the vital role that knowledge sharing plays in its growth and development.

Conclusion

The latest episode of the Solana Change Log provides a comprehensive overview of the recent developments and upcoming changes in the Solana ecosystem. From improvements in transaction processing and program deployments to the release of Web3.js v2 and performance optimizations, these updates demonstrate Solana's commitment to enhancing its infrastructure and developer experience.

As the blockchain landscape continues to evolve, Solana's focus on efficiency, scalability, and developer-friendly tools positions it as a leading platform for decentralized applications and blockchain innovation. The ongoing improvements and community engagement highlighted in this episode paint a promising picture for Solana's future growth and adoption.

Developers, validators, and Solana enthusiasts alike have much to look forward to as these changes roll out. The continuous refinement of the Solana protocol, coupled with new tools and resources, is set to unlock new possibilities and drive the next wave of blockchain innovation.

Facts + Figures

• SIMD191 proposes relaxing transaction constraints for loading failures, allowing validators to collect fees for processed transactions even if they fail.
• Program deployments on Solana are being improved, with the CLI version 2.2 of Agar introducing the ability to define skip pre-flight checks.
• A feature gate is being implemented to lift certain CPI call restrictions, improving efficiency by removing one of the checks during CPI calls.
• The program cache size for validators has been doubled, reducing the frequency of automatic program eviction and improving performance.
• The "executable" flag check is being optimized by relying on the owner check instead of storing a boolean value in each account.
• Web3.js version 2 is being released, offering faster and smaller performance compared to version 1.
• The Solana cookbook has been updated with tabs to show code snippets for both Web3.js v1 and v2 side by side.
• V-Logs, a new lightweight client for streaming Solana data, promises to reduce infrastructure costs by up to 50%.
• The Solana Stack Exchange continues to be an active community resource, with top contributors being recognized for their efforts.

Questions Answered

What is SIMD191 and how does it improve Solana?

SIMD191 is a proposal to relax transaction constraints for loading failures on Solana. It allows transactions that would previously fail before being included in a block to be processed and included, enabling validators to collect fees for the computation they perform. This change improves efficiency by ensuring validators are compensated for their work, even when transactions ultimately fail.

How are program deployments being improved on Solana?

Program deployments on Solana are being enhanced through several measures. The Solana CLI, starting from version 2.2 of Agar, will introduce the ability to define skip pre-flight checks. This change aims to simplify the process of landing transactions, particularly for program deployments. Additionally, workarounds are provided for both non-staked and staked nodes to improve deployment success rates and speed.

What changes are coming with Web3.js version 2?

Web3.js version 2 is a major update to the popular JavaScript library for interacting with Solana. It offers improved performance, being both faster and smaller than its predecessor. While it introduces some syntax changes, the Solana cookbook has been updated with side-by-side comparisons of v1 and v2 code snippets to assist developers in transitioning to the new version.

How is Solana improving its cache system for validators?

Solana is doubling the program cache size for validators. This change allows validators to store more data in their RAM for longer periods, reducing the frequency of automatic program eviction from the cache. As a result, this improvement enhances overall performance by keeping frequently used programs readily available in the cache.

What is V-Logs and how does it benefit Solana users?

V-Logs is described as a fast, lightweight client for streaming Solana data. It promises to reduce infrastructure costs by up to 50% compared to running full nodes or RPCs. This tool aims to make it easier and more cost-effective for developers to run their own indexers and analyze data on the Solana blockchain, potentially lowering the barrier to entry for building on Solana.