02Sheet 02.03.062 · Entries

A config-settings upgrade: Soroban transaction limit and three frozen trustlines

LEDGER_UPGRADE_CONFIG with two settings in one set: contract_execution_lanes (ledgerMaxTxCount 2) and frozen_ledger_keys (three trustlines).

FIG. · Where it sits · inside LedgerCloseMetaCAP-0046 · CAP-0077 · H-F10 · H-D12
LEDGER_UPGRADE_CONFIG updating contract_execution_lanes and frozen_ledger_keys
frozen-key list grown by a config upgrade

The shape

LEDGER_UPGRADE_CONFIG with two settings in one set: contract_execution_lanes (ledgerMaxTxCount 2) and frozen_ledger_keys (three trustlines). The new values appear only in upgradesProcessing, after the ledger's transactions.

Variants

VariantProtocolNetworkSourceSizesha256
p30-mainnet-generatedP30mainnet passphrasegenerated by stellar-core v30.0.01,080 B08399d01ec55…
p28-mainnet-generatedP28mainnet passphrasegenerated by stellar-core v30.0.01,072 Bdea1d5113301…
p30-testnet-generatedP30testnet passphrasegenerated by stellar-core v30.0.01,080 Bc851004f708f…
p28-testnet-generatedP28testnet passphrasegenerated by stellar-core v30.0.01,072 B2d2f993832d5…

What a correct reader returns

A correct reader findsValueBacked by
One upgrade, a config upgrade.length 1constructionsnapshot
It sets ledger_max_tx_count 2.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.config-lanes-and-freeze · compiled from catalog/upgrade.config-lanes-and-freeze.json · entry.json

On this page