It's time to get ready for the Stellar network upgrade to Protocol 17! This version of the protocol includes a new Asset Clawback feature that we're documenting in detail, and we're excited to talk more about it in subsequent posts, but for now, we want to share key dates and action items to give you time to prepare.
If you develop on Stellar, you need to install up-to-date versions of all Stellar-related software — including Stellar Core, Horizon, and any Stellar SDKs you use — in advance of the network upgrade. If and when validators vote to accept Protocol 17, the upgrade takes effect immediately, and since all the new software is backwards compatible with the current protocol, the best course of action is to update sooner than later. Doing so will ensure your Stellar integration keeps on ticking when the network levels up.Key dates May 4, 2021 — Testnet upgrade June 1, 2021 — Public network upgrade vote Protocol 17 Releases
We've gathered a list of software that requires updating below. Please make sure to check release notes for specific instructions and relevant details to ensure you understand all relevant requirements.Stellar infrastructure
Node operators need to install the latest version of Stellar Core and/or Horizon. For setup-specific details, see the sections below.SDKs
For developers, links to minimum SDK versions are here. We will continue to add links to releases as soon as they come out.If you run Horizon
Upgrade to Horizon v2.2.0 which has full support for Protocol 17. If you are running a pre-v2.2.0 version of Horizon when the network upgrades, your Horizon instance will not be able to ingest or query asset clawback operations, and will crash when it encounters one.
By default, v2.2.0 deploys Horizon's new architecture. It runs a mini-Stellar Core (aka Captive Core) as a subprocess of Horizon, so you don't need to run a standalone Stellar Core node, and you don't ne...