Anza Github Migration FAQ

Why is Anza closing the PRs from the previous Solana Labs repo? It’s much simpler to only allow new commits on one repo at a time. The weekend of March 2 we’ll switch from solana-labs/solana to anza-xyz/agave. PRs that aren’t yet merged will need to be re-created in the agave repo.

What will happen to the outstanding issues? We will judiciously filter and migrate relevant issues into the new repo on an ongoing basis, not all of them will be transferred over and some will be closed.

If I have a new PR, should I submit it to Agave or to the old Solana Labs repo and why? New PRs should go to anza-xyz/agave. The solana-labs/solana repo will be archived soon.

What will happen to the old Solana Labs repo? The Solana Labs monorepo will eventually become inactive. It won’t be archived immediately since issues there will be easier to wind down in situ, but soon it will be archived. This will be a several months long process where the Agave client mirrors the Solana Labs client before the two diverge and the Solana Labs client becomes fully inactive

Will the developer discussions for the Agave fork occur in the Solana Discord or in the Anza Discord? For the time being we will continue to use the Solana Tech Discord for most discussions. This may change later in the year.

Is the Agave fork the “official” Solana client repo going forward? There is no “official” Solana repo, but Anza will primarily be working on its version of the Solana client in anza-xyz/agave.

Is there a roadmap or engineering plan for the Agave client? Where can I learn more about the future plans for the Agave client? The Solana Tech Discord and Anza GitHub will be the best place to stay up to date for now.

When will the Agave client be released? What is the overall plan and timeline? Agave is the continuation of the Solana Labs validator client as managed by Anza. For the first stage, Agave release numbers will match the Solana Validator numbers. This includes v1.17 and v1.18. This means Agave releases will be mirrored to the Solana Labs repo in parallel, giving operators time to switch to Agave. Agave and Solana Validator v1.17 and v1.18 will be identical in terms of functionality. In the Summer or 2024, we will release Agave v2.0 at which point Solana Validator will be archived and we recommend 100% of the network have migrated fully to Agave.

What alerting system should I use for future validator releases? Where can I subscribe to this? For now, please continue to use the existing alert system. We may create our own system later this year, please stay tuned for more updates (please subscribe here to receive updates from Anza (https://www.anza.xyz/subscribe).

Is there a new branch/fork that we should upgrade to now? If not, where can I get more information about that? Until the first agave client release happens you should stay up to date on the latest Labs client stable release.

What happens when Agave is launched? Will it impact my validator running an older version of the Labs client? Not immediately, but older versions will eventually become incompatible as new feature gates get activated.

How will this impact the current Feature Gate Activation Schedule There will be no impact on the schedule.

Are there plans to separate the RPC node from the Agave client and what are they? The current plan is to eventually separate the RPC portion of Agave into a separate project. No immediate action is necessary.

Should I still attend the Solana Developer // Core Engineering calls or will Anza have separate calls for the developers? Please continue attending the regular calls, our team will join as needed.

What license will Agave be released under? Apache 2.0.

How will this affect the development of the Firedancer and other clients? This will not impact Firedancer or other clients.

I run RPC nodes, does this affect me? Please continue using the latest Solana Labs client release until the first Agave client release is made public.