02Sheet 02.03.067 · Entries

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,…

FIG. · Where it sits · inside LedgerCloseMetapre-cap · CAP-0046 · H-F1 · H-F6
LEDGER_UPGRADE_VERSION 0 -> 30 and LEDGER_UPGRADE_BASE_RESERVE in one ledger; initial ConfigSettingEntry rows created
upgradesProcessing changes in a different order in every core run

The shape

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, all in upgradesProcessing. Its change order differs in every core run (20 of 20), its content never.

Variants

VariantProtocolNetworkSourceSizesha256
p30-mainnet-generatedP30mainnet passphrasegenerated by stellar-core v30.0.0
change order varies: 20 orderings in 20 runs
5,268 B07e04296cf8b…
p30-testnet-generatedP30testnet passphrasegenerated by stellar-core v30.0.0
change order varies: 2 orderings in 2 runs
5,268 B3769a1d92d7c…

What a correct reader returns

A correct reader findsValueBacked by
The header's ledger version becomes 30.30constructionsnapshotcorewalker
One upgrade sets the base reserve to 5000000 stroops.some change where 1 fields matchconstructionsnapshotcorewalker
The initial contract_max_size_bytes setting is created.some change where 1 fields matchconstructionsnapshotcorewalker

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 walker

Entry id upgrade.generated-protocol-30 · compiled from catalog/upgrade.generated-protocol-30.json · entry.json

On this page