04Sheet 04.07 · Hazards

Layer F: Ledger level

Every hazard in layer F of the registry, each with its evidence and the test the corpus holds or will hold for it.

Upgrade ledgers, empty and very large ledgers, parallel Soroban stages, change order that varies between core processes, and the same ledger in different bytes.

H-F1in the corpusreplay probe
Protocol-upgrade ledgers (config settings, version, StellarValueExt)
EvidenceR02 ('3' is not a valid StellarValueType)
TestMainnet M:protocol-upgrade (P→current), testnet P30 upgrade; never generated (non-deterministic)
H-F2in the corpusconformance
P30 StellarValue signed_ms (CAP-0088)
EvidenceR01
TestTestnet M:protocol-30-signed-ms; every P30 recipe ledger
H-F3in the corpusreplay probe
Large ledgers (memory, many transactions)
EvidenceN4
TestMainnet M:largest-ledger
H-F4in the corpusreplay probe
Empty ledgers (no transactions)
EvidenceSTELLAR_VALUE_EMPTY_TX_SET* arms
Testc-base empty-ledger; s-base archival-empty-ledgers (16 ledgers whose only content is eviction)
H-F5in the corpusreplay probe
Parallel Soroban execution stages (several stages, several clusters)
EvidenceR08 objection 3
TestMined mainnet: pubnet 65485185 has 3 stages with 1, 2 and 1 clusters; pubnet 65506631 and 65517506 have 2 clusters in one stage. Generated ledgers put independent transactions in one cluster unless instruction budgets force bins apart, and equal bids make that split depend on a random tie-break (ParallelTxSetBuilder.cpp:717)
H-F6in the corpusreplay probe
Change order within an operation varies between core processes
EvidenceR09
TestOrder-variant raw bytes shipped as variants
H-F7in the corpusconformancereplay probe
LedgerCloseMetaExt v1 (Galexie) vs v0 (RPC) for the same ledger
EvidenceR01
TestEvery run under the base profile (LedgerCloseMetaExt v1) and the bare profile (v0); same header hash, different bytes (recipes/flags)
H-F8in the corpusreplay probe
Meta version polymorphism on backfill: LCM v0/v1, TxMeta v2/v3, V0 envelopes, refunds in txChangesAfter (P20–22)
Evidenceledger-close-meta.md:85-105
TestMined: pubnet 26588352 (P12: LedgerCloseMeta v0, 532 TransactionEnvelope V0) and pubnet 56085459 (P22: LedgerCloseMeta v1, Soroban fee refunds in txChangesAfter for 53 transactions). Every lake object inspected (protocols 12, 22 and 29) carries TransactionMeta v4, because Galexie sets BACKFILL_STELLAR_ASSET_EVENTS, which makes stellar-core emit v4 (TransactionMeta.cpp:532-536; the lake objects name stellar-core 23.0.1 as writer); a default node writes v2 before protocol 20 and v3 for 20-22, for the same ledgers
H-F9in the corpusreplay probe
Same ledger, different bytes by node flags (six Galexie flags vs RPC defaults)
Evidenceledger-close-meta.md:390-406
TestEvery run under three profiles (recipes/flags: base, galexie, bare), compared on normalised content by tools/profile-compare.mjs in make generate (recipes/<lane>/profiles/p30-mainnet.json): every ledger keeps the same header hash; bare differs from base in every ledger but the protocol-upgrade one; galexie differs from base in no classic ledger and in the 46 Soroban ledgers with contract calls (diagnostic events); variant keys carry the profile suffix
H-F10in the corpusreplay probe
Config-settings upgrade ledgers (LEDGER_UPGRADE_CONFIG; changes in upgradesProcessing)
Evidence18 ConfigSettingEntry arms uncovered
TestGenerated: two LEDGER_UPGRADE_CONFIG ledgers whose upgradesProcessing updates contract_execution_lanes and frozen_ledger_keys, staged by kit2 as a temporary entry (Upgrades.cpp ConfigUpgradeSetFrame::makeFromKey): s-base config-upgrade-lanes-and-freeze, config-upgrade-restore-and-unfreeze; mined: pubnet 65080525, a settings vote updating 7 entries in one upgrade (including ledger_max_dependent_tx_clusters 3), and pubnet 65273932, whose upgrade grows the frozen-key list from 3 to 4 accounts

The hazards come straight from caps/registry.json. A tag says which check will exercise each one: replay probe, conformance, linter, guide or verify facts. In the corpus means an entry already targets it.