Agave Transition

Overview

Core development of the solana-labs/solana monorepo has transitioned to the anza-xyz/agave fork. New commits to the v1.18 branch will be synced from anza-xyz/agave to solana-labs/solana and all v1.18.x releases will be duplicated between the two repos. The release commit hashes don't match between the repos because of crate renames and CI changes, but binaries with matching version numbers are functionally equivalent.

Crates Renamed

Six of the crates have been renamed:

Original Name	New Name
solana-validator	agave-validator
solana-ledger-tool	agave-ledger-tool
solana-watchtower	agave-watchtower
solana-install	agave-install
solana-geyser-plugin-interface	agave-geyser-plugin-interface
solana-cargo-registry	agave-cargo-registry

Migration

Releases will continue in parallel until the end of v1.18 at which point the solana-validator releases will be discontinued. Operators should switch to agave-validator before upgrading to v2.0.

Approximate mainnet-beta rollout date	Labs Client	Agave
2024-01-15	v1.17	v1.17
2024-06-15	v1.18	v1.18
2024-10-01	-	v2.0
2025-01-01	-	v2.1

Migration Steps

Operators can switch to Agave any time before upgrading to v2.0 (when solana-validator will be discontinued). The exact steps will vary depending on the configuration, but most operators will need these changes:

• If you build from source, switch to the new repo: anza-xyz/agave.
• If you use solana-install then switch to agave-install. Use this command for your next upgrade (replace X, Y, and Z with the version numbers). After using this once you can use agave-install for subsequent upgrades.
  • sh -c "$(curl -sSfL https://release.anza.xyz/vX.Y.Z/install)"
• Update scripts that reference solana-validator or any of the other renamed binaries.
• Update systemd configs if they reference the binary names (eg solana-validator exit).
• If you specify RUST_LOG in your configs update it to include agave. The default is now solana=info,agave=info.