Protocol 30 today
The Protocol 30 CAPs that change what a ledger reader sees each have a coverage row. Each row holds at least one
entry that the pinned stellar-core emitted at Protocol 30, with testnet and mainnet twins:
Variants that use these shapes declare it in
requires (sc_address_type_muxed_contract,
stellar_value_signed_ms). Each conformance driver probes its SDK’s generated XDR for the same features, so an SDK
released before Protocol 30 is excused from decoding them, and an SDK that claims Protocol 30 is not.
Fail loudly, never silently
Every place where the kit encodes Protocol 30 fails when a new protocol arrives:
The tools that read the live network (
xdrcheck-corpus capture, xdrcheck-corpus mine) are the one exception: they
read a ledger above the gate with a warning, so an upgrade made with little notice does not stop them, and they never
make a corpus entry from it. A LedgerCloseMeta v3 has been drafted on a stellar-xdr branch but is in no
stellar-core release; the meta-version gate refuses it until it is reviewed.
How the kit sees an upgrade coming
Measured over Protocols 22 to 30 (docs/maintenance.md, section 5.5):
Upgrades without XDR changes come with the least notice: about two days for Protocol 24, none for Protocol 29.
Upgrade tooling
All of these run by hand. None has a schedule and none gates a pull request.
The next upgrade, step by step: Protocol 30 to 31
Each step has an output that can be inspected.
Rules that hold throughout: released entries are never edited; entries at older protocols stay and keep being
verified; an expectation whose meaning changes at the new protocol becomes a new entry with its protocol range.
Number-only upgrades. When
xdrcheck xdr diff <old tag> <new tag> is empty (as for Protocols 24 and 29), the
upgrade takes a day: move stellar-core, raise the gates and the constants xdrcheck pins check names, regenerate,
capture the upgrade ledger on both networks, run the corpus and conformance checks, and release.
Dated events already recorded. The mainnet vote on Protocol 30 (2026-11-23) and the next testnet reset
(2026-12-16) are [[schedule]] events in pins.toml. From 14 days before each, xdrcheck pins check warns; after
the day it fails until the pin has moved. Testnet history entries are vendored with their epoch, so the corpus
stays complete after the reset.
What an SDK gets at each upgrade
Before the protocol ships, a-next release (N.0.0-rc.K) carries the new shapes; after it, the stable N.0.0. Your
SDK’s CI runs the release with a loader and your committed expected-failure list: every Protocol N entry your SDK
cannot read shows as a new failure until your update lands, and a listed entry that starts to pass fails the run
until you remove its line. An unreleased branch can be tested with --sdk <checkout>. Text for a per-SDK protocol
compatibility issue: Protocol upgrades for SDKs.
What an indexer gets at each upgrade
The upgrade ledger and the first ledgers after it are captured from the public lake on testnet as soon as testnet upgrades (step 6), and local-core entries at the new protocol exist from step 5. Replay them through your indexer before the mainnet vote. An indexer whose pinned go-stellar-sdk cannot decode the new protocol declares that in its adapter’s envelope (sdk_limit), so the gap is reported as not_applicable per entry, not hidden. The readiness
matrix (step 9) lists which pipeline commits read the new protocol.