Solana is ready for a significant update with the release of Agave v2.0, a new validator client developed by Anza that is poised to enhance the network's performance and security. Scheduled to go live on the Solana Mainnet-Beta in early October, this transition marks a big step forward for the Solana ecosystem. For developers utilizing Solana endpoints on Ankr's Web3 API services, it's important to stay informed and take any necessary steps to ensure a smooth transition during this update.

Use Ankr’s Solana RPC →

What Is Agave 2.0?

Agave v2.0 is a major upgrade from the original Solana Labs validator client, bringing performance improvements while maintaining backward compatibility with existing Solana dApps. However, this update introduces several breaking changes, including RPC endpoint deprecations, SDK adjustments, and crate renaming, which could require updates to scripts and applications used by developers.

Moreover, the original Solana Labs GitHub repository will be archived, with all ongoing development shifting to Anza’s Agave client repository. This change underscores the broader effort to diversify Solana's validator clients, contributing to increased network resilience and reliability.

Key Changes and What They Mean for Developers

Agave v2.0 introduces several changes that may require action from developers using Ankr's Solana RPC services:

1. Removed RPC Endpoints and Replacement Calls

Several RPC endpoints that were part of Agave v1.0 have been deprecated and will be removed in v2.0. Developers should update their code to use the new replacement calls provided by Agave v2.0.

Here's a quick overview of some important changes:

Table and more info in our docs.

These changes will ensure that your RPC interactions remain functional and optimized for the new Agave client, so it’s important to adjust your scripts before Agave v2.0 goes live.

2. SDK and Codebase Updates

Agave v2.0 also brings changes to the Solana SDK, removing support for Borsh v0.9 and deprecating several symbols in solana-sdk and solana-program. Developers are encouraged to switch to Borsh v1 or v0.10 and review any deprecated symbols in their code. The transition to Agave is a great opportunity to update your development environment to the latest standards, ensuring compatibility with future Solana innovations.

3. Renamed Crates

As Solana expands its validator client offerings, crate renaming has been introduced to differentiate Agave-related dependencies from those maintained by other teams. Below are some of the key crate renames:

Table and more info in our docs.

Make sure to update your dependencies to reference the new crate names to avoid any compatibility issues during the transition.

Deprecated Validator Arguments

Agave v2.0 will also remove several deprecated validator arguments, some of which may impact your configurations. For example, the following commands will no longer be available:

Table and more info in our docs.

If you rely on any of these commands, you should review and update your validator configurations accordingly to prevent any disruptions when Agave v2.0 is deployed.

Preparing for the Agave v2.0 Transition

The transition to Agave v2.0 will affect all validator operators and developers working with Solana. If you're using Ankr's RPC services, now is the time to review and update your apps to account for the removed RPC endpoints, renamed crates, and deprecations.

We recommend the following steps to prepare for this transition:

• Audit your current RPC calls: Identify any deprecated endpoints in your scripts or applications and update them to the new Agave v2.0 equivalents.
• Update your SDK and dependencies: Ensure you’re using the latest versions of the Solana SDK and update your dependencies to reference the new Agave-related crate names.
• Revise validator configurations: If you're operating a validator, review your arguments and configurations to remove any deprecated commands.

To check out the full list of changes, including more detailed technical documentation, please consult the Agave v2.0 changelog.

Final Thoughts

The Agave v2.0 update is a testament to Solana’s commitment to continually improving its blockchain performance and security. While this transition introduces several changes for devs, it ultimately strengthens the network's infrastructure and opens the door for future innovations. By staying proactive and updating your scripts and apps ahead of the release, you can ensure that your experience on Solana remains seamless.

Join the Conversation on Our Channels!

Twitter | Telegram | Substack |  Discord | YouTube | LinkedIn | Reddit | All Links