The mainnet ledger that upgraded the protocol to 29
A protocol upgrade applies at the end of a ledger: LEDGER_UPGRADE_VERSION in the header's scp_value.upgrades, and the changes it causes in upgradesProcessing.
The shape
A protocol upgrade applies at the end of a ledger: LEDGER_UPGRADE_VERSION in the header's scp_value.upgrades, and the changes it causes in upgradesProcessing. The ledger's own transactions ran under the old protocol.
Variants
| Variant | Protocol | Network | Source | Size | sha256 |
|---|---|---|---|---|---|
p29-mainnet-mined-l64717645 | P29 | mainnet passphrase | mined from history | 881,080 B | 78500116981a… |
What a correct reader returns
| A correct reader finds | Value | Backed by |
|---|---|---|
| The header's ledger version is 29. | 29 | snapshotcorewalker |
| upgradesProcessing holds the version upgrade. | [object Object] | snapshotcorewalker |
Check it yourself
make verify # schema, hashes, the byte-for-byte round trip and every fact above
make oracle # the facts' values, re-read by stellar-core and the schema walkerEntry id upgrade.protocol-29-mainnet · compiled from catalog/upgrade.protocol-29-mainnet.json · entry.json
A fresh network's upgrade ledger: protocol 0 to 30 and base reserve 0.5 XLM
The first upgrade of a fresh standalone network sets the protocol to 30 and the base reserve in one ledger; crossing the Soroban protocol creates every Soroban config setting at its initial value,…
The testnet ledger that upgraded the protocol to 30
LEDGER_UPGRADE_VERSION 30 on testnet, written by a Galexie node.