What's New

What's New

Agave v2.0 transition guide

Agave v2.0 is a major validator client update scheduled to be released on Solana Mainnet-Beta in early October. Agave v2.0 is designed to improve the network's performance and security while maintaining backward compatibility for applications on Solana. This update is crucial for validator operators and developers, as the original Solana Labs GitHub repository will be archived, and all further development will shift to Anza’s Agave client repository.

Agave v2.0 contributes to Solana’s efforts to enhance block space utilization and efficiency, and its introduction is part of a broader move toward diversifying the validator clients on Solana's network.

Agave v2.0 update contains a number of breaking changes, such as deprecation of RPC endpoints, crate renaming, and validator arguments removal, which may require Solana developers to update their scripts. The article's info is based on Anza's recently released transition guide (opens in a new tab).

Removed RPC endpoints and SDK items

RPC endpoints changes:

A number of deprecated Agave v1.0 endpoints are set to be removed. These endpoints are recommended to be replaced in the following manner:

Deprecated v1 API Callv2 Replacement Call
confirmTransactiongetSignatureStatuses
getSignatureStatusgetSignatureStatuses
getSignatureConfirmationgetSignatureStatuses
getConfirmedSignaturesForAddressgetSignaturesForAddress
getConfirmedBlockgetBlock
getConfirmedBlocksgetBlocks
getConfirmedBlocksWithLimitgetBlocksWithLimit
getConfirmedTransactiongetTransaction
getConfirmedSignaturesForAddress2getSignaturesForAddress
getRecentBlockhashgetLatestBlockhash
getFeesgetFeeForMessage
getFeeCalculatorForBlockhashisBlockhashValid or getFeeForMessage
getFeeRateGovernorgetFeeForMessage
getSnapshotSlotgetHighestSnapshotSlot
getStakeActivationgetAccountInfo (alternative approach (opens in a new tab))

SDK changes:

See a complete list of breaking changes on the Agave changelog (opens in a new tab).

Renamed crates

Agave v2.0 brings renaming for a number of crates to accommodate the introduction of multiple Solana validator clients and ensure clarity in distinguishing Agave-related dependencies from those managed by other teams.

Original NameNew Name
solana-validatoragave-validator
solana-ledger-toolagave-ledger-tool
solana-watchtoweragave-watchtower
solana-installagave-install
solana-geyser-plugin-interfaceagave-geyser-plugin-interface
solana-cargo-registryagave-cargo-registry

Removed validator arguments

These deprecated validator arguments will be removed upon the release of Agave v2.0:

Commands
--enable-rpc-obsolete_v1_7 (#1886 (opens in a new tab))
--accounts-db-caching-enabled (#2063 (opens in a new tab))
--accounts-db-index-hashing (#2063 (opens in a new tab))
--no-accounts-db-index-hashing (#2063 (opens in a new tab))
--incremental-snapshots (#2148 (opens in a new tab))
--halt-on-known-validators-accounts-hash-mismatch (#2157 (opens in a new tab))

GitHub: Solanda Labs –> Anza Agave

Over recent months, Anza's core engineers and Solana ecosystem developers have been progressively migrating the Agave validator client from the Solana Labs to Anza Agave repository. Once the Agave v2.0 update is released on Mainnet-Beta, the Solana Labs GitHub repository will be archived and no longer used.