02Sheet 02.03.069 · Entries
The testnet ledger that upgraded the protocol to 30
LEDGER_UPGRADE_VERSION 30 on testnet, written by a Galexie node.
FIG. · Where it sits · inside LedgerCloseMetaCAP-0088 · H-F1
LEDGER_UPGRADE_VERSION 30 on testnet
The shape
LEDGER_UPGRADE_VERSION 30 on testnet, written by a Galexie node.
Variants
| Variant | Protocol | Network | Source | Size | sha256 |
|---|---|---|---|---|---|
p30-testnet-mined-l5540313 | P30 | testnet passphrase | mined from history | 345,344 B | 0f2ed6010b72… |
What a correct reader returns
| A correct reader finds | Value | Backed by |
|---|---|---|
| upgradesProcessing holds the version 30 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-30-testnet · compiled from catalog/upgrade.protocol-30-testnet.json · entry.json
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.
A trapped mainnet call whose diagnostic events carry the contract's own error code
The contract fails with its own error (SCError type contract, code 2006).