02Sheet 02.04 · Corpus

Mined ledgers

37 real mainnet and testnet ledgers from the public data lake, for shapes a standalone generator cannot produce, or that are worth having as real network bytes: eviction at the cap, settings votes, a mainnet freeze, protocol-12 V0 envelopes.

37
ledgers
47
shape records
34 · 3
mainnet · testnet
P12 P22 P28 P29 P30
protocols

Some shapes only happen on a real network, and some are worth having as real network bytes. Examples:

  • eviction at the per-ledger cap;
  • validator settings votes;
  • a mainnet freeze of ledger keys (CAP-0077);
  • protocol-12 V0 envelopes;
  • protocol-22 refunds;
  • multi-stage parallel Soroban phases.

mined/ holds those as real LedgerCloseMeta, fetched from SDF's public data lake and located with BigQuery over the public Hubble dataset. The queries are in mined/queries/.

FileWhat it is
mined/ledgers/<network>-<seq>.lcm.xdr.zstOne ledger, zstd-compressed. Its sha256 and size describe the decompressed bytes: the lake object minus its 12-byte batch header
mined/index.jsonOne record per shape found in a ledger: the lake URL, the stellar-core version that wrote it, how it was located, the findings with exact JSON paths, and why readers break on it

make verify also runs tools/mined-verify.mjs. Every file must match its hash, round-trip byte for byte through native rs-stellar-xdr, and carry the recorded sequence and protocol. Every finding's transaction and JSON path must be present. make coverage reports the union arms these ledgers reach: 289 of 499.

Network data, not entries

These ledgers were written by SDF's Galexie with its default flags, so their metadata differs from a default node's (see Found while building). Most are not corpus entries: entries carry facts and hazards, and these carry findings. The catalog also compiles entries from them: 37 entries so far, built from 22 of these ledgers, the signed-payload signer among them.

Every mined shape

ShapeLedgerWhy readers break
fee bump inner failed
17× in this ledger
mainnet 65517511
P29 · LCM v2 · 365 txs
The outer result is txFEE_BUMP_INNER_FAILED and the real result (inner hash, inner code, per-op codes) sits one level down in InnerTransactionResultPair; readers that only look at the outer code or outer hash report the wrong hash, fee or success flag.
muxed accounts
3× in this ledger
mainnet 65517507
P29 · LCM v2 · 409 txs
M-addresses appear only in the envelope (operation source, payment destination); the meta shows the base G-account and the id moves to the event's to_muxed_id, so readers that key on 32-byte accounts truncate, drop the id or double-count the participant.
muxed accounts
1× in this ledger
mainnet 65517493
P29 · LCM v2 · 347 txs
The transaction source is a muxed account: the sequence number and fee belong to the underlying G-account, and code that stores the source as a fixed 32-byte key or compares strkeys as text mismatches it.
muxed accounts
5× in this ledger
mainnet 65517347
P29 · LCM v2 · 530 txs
The fee-bump fee source is muxed; fee attribution must resolve it to the G-account that is debited in fee_processing.
claimable balance predicates
32× in this ledger
mainnet 65490107
P29 · LCM v2 · 188 txs
ClaimPredicate is a recursive union (and[not(relative), relative]); flat schemas (Hubble's fixed-depth record) and non-recursive decoders drop or mis-nest the inner predicate, and relative time must not be read as an absolute timestamp.
claimable balance predicates
1× in this ledger
mainnet 65509146
P29 · LCM v2 · 554 txs
An or predicate holding a not(absolute time) and a bare unconditional arm in the same vector; readers that expect every element to be an object, or that flatten or/not, lose the second branch.
claimable balance claim
2× in this ledger
mainnet 65517506
P29 · LCM v2 · 260 txs
The claim names only a 32-byte balance id; asset, amount and claimant must be recovered from the removed ClaimableBalanceEntry in the operation's meta changes, which readers that work from the envelope alone cannot do.
liquidity pool
1× in this ledger
mainnet 65517493
P29 · LCM v2 · 347 txs
Pool-share trustlines carry a LiquidityPoolParameters body instead of an asset and are keyed by pool id; deposits and withdrawals change two reserves at once, so asset-keyed trustline readers and single-asset balance readers mis-handle them.
liquidity pool
1× in this ledger
mainnet 65516375
P29 · LCM v2 · 281 txs
A pool-share trustline is removed (change_trust limit 0) right after a full withdraw; readers must delete a trustline whose key is a pool id, not an asset code and issuer.
path payment long path
60× in this ledger
mainnet 65517347
P29 · LCM v2 · 530 txs
A path of 5 intermediate assets yields a chain of ClaimAtoms (order-book and pool) across up to 6 hops in one operation result; readers that assume one trade per payment or a single asset pair attribute the amounts to the wrong assets.
account merge
4× in this ledger
mainnet 65514426
P29 · LCM v2 · 427 txs
The amount moved is not in the operation (the body is only a destination); it exists only in the result's success arm and the account entry is removed, so readers miss the balance transfer or keep a deleted account.
bump sequence
1× in this ledger
mainnet 65515672
P29 · LCM v2 · 395 txs
The account's sequence number jumps to an arbitrary int64 with no payment or balance change; readers that derive sequence numbers by counting transactions go out of step.
manage data binary
1× in this ledger
mainnet 65506631
P29 · LCM v2 · 564 txs
DataValue is opaque<64>, here 64 random bytes; readers that treat it as a UTF-8 string corrupt it (replacement characters) or fail to store it.
memo text non utf8
1× in this ledger
mainnet 65024796
P29 · LCM v2 · 292 txs
Memo text is string<28> of raw bytes and this one starts with 0xFF, which is not valid UTF-8; SDKs that decode it to a native string re-encode it as EF BF BD and change the transaction hash (js-stellar-sdk#1823), and Hubble stores U+FFFD.
memo hash return
1× in this ledger
mainnet 65517493
P29 · LCM v2 · 347 txs
MEMO_RETURN is a 32-byte hash arm that many readers never see; code that switches only on none/text/id/hash drops it or prints it as text.
memo hash return
1× in this ledger
mainnet 65517499
P29 · LCM v2 · 349 txs
MEMO_HASH is 32 raw bytes; readers that coerce memos to strings corrupt it, and hex versus base64 rendering differs between tools.
clawback and trustline flags
3× in this ledger
mainnet 65517152
P29 · LCM v2 · 361 txs
Clawback burns an asset from a holder with the issuer as source (the from field is a MuxedAccount) and clawback_claimable_balance removes a balance entry nobody claimed; readers that model balance decreases only as payments or claims lose these.
sponsorship
2× in this ledger
mainnet 65517153
P29 · LCM v2 · 340 txs
Begin/end sponsoring changes who pays the reserve for entries created by the operations in between, visible only as sponsoring_id and num_sponsored/num_sponsoring in entry extensions; revoke_sponsorship carries a LedgerKey or (account, signer) union that op-level readers often do not decode.
signer hashx preauth
15× in this ledger
mainnet 65517491
P29 · LCM v2 · 327 txs
The signer key is a hash-x (X...) key, not an ed25519 account; readers that store signers as G-addresses or 32-byte account ids mis-encode or reject it.
signer hashx preauth
6× in this ledger
mainnet 65485185
P29 · LCM v2 · 329 txs
The signer key is a pre-authorized transaction hash (T...); it is removed automatically when that transaction applies, so signer lists change without a set_options operation.
soroban restore footprint
1× in this ledger
mainnet 65419251
P29 · LCM v2 · 163 txs
The operation body is empty (ext only); what is restored is defined by the transaction's read_write footprint and shows up as restored ledger-entry changes plus TTL entries, which readers that expect created/updated/removed/state only do not handle.
soroban extend footprint ttl
1× in this ledger
mainnet 65514034
P29 · LCM v2 · 220 txs
Only TTL entries change (keyed by the sha256 of the ledger key, not by the key itself), so readers that match changes by contract id see nothing happen.
soroban wasm upgrade
1× in this ledger
mainnet 65514477
P29 · LCM v2 · 351 txs
The contract instance's executable hash changes in place and the only event is a system-type executable_update event; readers that filter on contract-type events or cache the wasm hash per contract miss the upgrade.
soroban wasm upgrade
1× in this ledger
mainnet 65514426
P29 · LCM v2 · 427 txs
upload_contract_wasm carries the whole wasm blob inside the operation and creates a ContractCode entry keyed by its sha256; readers with small per-field size limits or that assume every host function is invoke_contract fail on it.
soroban auth many entries
700× in this ledger
mainnet 65167655
P29 · LCM v2 · 1184 txs
One invocation carries 26 address-credential auth entries (51 authorized invocations), each with its own nonce and signature ScVal; readers that take auth[0] as the signer, or cap the vector, lose 25 participants.
soroban auth deep nesting
1× in this ledger
mainnet 65515672
P29 · LCM v2 · 395 txs
SorobanAuthorizedInvocation is recursive (sub_invocations three levels deep here); non-recursive walkers miss the inner contract calls and the assets they move.
soroban event deep scval
1× in this ledger
mainnet 65516072
P29 · LCM v2 · 312 txs
The event data is an ScVal nested five containers deep (maps of vecs of maps); readers that convert ScVal to native types with a fixed depth, or that sort or deduplicate map keys, truncate or reorder it.
soroban sac transfer muxed
1× in this ledger
mainnet 65146228
P29 · LCM v2 · 425 txs
A contract sends USDC through the SAC to an M-address: the topic holds the base G-account and the id is in a data map as to_muxed_id = 13810323384076279538 (above 2^63), so the data is a map instead of a bare i128 and the id overflows signed 64-bit readers (stellar-etl#460: address_muxed always null).
soroban sac transfer muxed
1× in this ledger
mainnet 65392674
P29 · LCM v2 · 318 txs
A native-asset SAC transfer from a G-account to an M-address inside invoke_host_function; the event data changes shape from i128 to a map with amount and to_muxed_id, which breaks readers that expect the pre-CAP-0067 layout.
soroban failed
1× in this ledger
mainnet 65517387
P29 · LCM v2 · 342 txs
Failed Soroban transactions still appear in tx_processing with fees charged, a SorobanTransactionMeta ext and diagnostic events but no return value and no contract events; readers that assume soroban_meta implies success, or that count diagnostic events as real events, report phantom transfers.
soroban failed
1× in this ledger
mainnet 65511929
P29 · LCM v2 · 491 txs
The result code is entry_archived, a code many enum tables lack; the transaction failed because a footprint entry had been evicted to the hot archive.
soroban failed
1× in this ledger
mainnet 65516072
P29 · LCM v2 · 312 txs
The invocation ran but failed afterwards with insufficient_refundable_fee; fee accounting (non-refundable charged, refundable zero) differs from a trap and readers that recompute fees from the envelope get the wrong charge.
protocol upgrademainnet 64717645
P29 · LCM v2 · 145 txs
The header already says ledger_version 29 while the upgrade itself is in scp_value.upgrades and upgrades_processing, whose changes (config settings) belong to no transaction; readers that only walk tx_processing miss state changes, and readers that pick the decoder by header version must switch on exactly this ledger.
protocol upgradetestnet 5540313
P30 · LCM v2 · 28 txs
Testnet's upgrade to Protocol 30: ledger_version is 30 but StellarValue.ext is still the old signed arm (the next ledger is the first with signed_ms), and the upgrade rewrites three config-setting entries outside any transaction.
protocol 30 signed mstestnet 5540314
P30 · LCM v2 · 14 txs
First testnet ledger whose StellarValue.ext uses the Protocol 30 signed_ms arm (CAP-0088 millisecond close time); every decoder generated from XDR older than v30 fails the whole ledger with 'xdr value invalid' (stellar CLI 27 measured in 01-corpus-capture.md).
largest ledgermainnet 65167655
P29 · LCM v2 · 1184 txs
The largest ledger of the last 30 days by operation count (1,478 operations in 1,184 transactions, 5.57 MB of LedgerCloseMeta); readers with message-size caps, per-ledger timeouts or quadratic change matching fail or stall on it.
alphanum12 asset
225× in this ledger
mainnet 65517511
P29 · LCM v2 · 365 txs
Asset codes of 5 to 12 characters use the 12-byte AlphaNum12 arm, zero-padded; readers that assume 4-byte codes, or that do not strip or keep the padding consistently, split one asset into two.
offer crosses many
1× in this ledger
mainnet 65488299
P29 · LCM v2 · 158 txs
One manage_sell_offer claims 638 order-book offers in a single operation result and leaves a residual offer; readers that expect one trade per operation, or cap offers_claimed, lose trades and get balances wrong.
signed payload signer
1× in this ledger
testnet 4437357
P28 · LCM v2 · 12 txs
The signer key is an ed25519 signed-payload key (P..., key plus up to 64 payload bytes); wallet-backend's fixed 32-byte address column could not encode it and ingestion retried this ledger forever (wallet-backend#729, #716).
signed payload signer
7× in this ledger
mainnet 65483028
P29 · LCM v2 · 634 txs
PreconditionsV2.extra_signers holds two signed-payload (P...) signer keys on a mainnet transaction; Hubble's account_signers table shows no P-keys at all, so this precondition field is the only mainnet place the type appears.
soroban auth address v2
3× in this ledger
mainnet 65517506
P29 · LCM v2 · 260 txs
The auth entry uses the address_v2 credentials arm instead of address; readers with a two-arm switch (source_account, address) skip the signer or fail to decode the entry.
int64 max limitmainnet 65517506
P29 · LCM v2 · 260 txs
A trustline limit of 9223372036854775807 stroops (INT64_MAX) cannot be held in a float64; stellar-etl converts amounts to float and loses stroop precision (stellar-etl#454), and JavaScript numbers round it to 9223372036854775808.
evicted keys at cap
2000× in this ledger
mainnet 65460631
P29 · LCM v2 · 162 txs
Entries leave the live state with no transaction: 1000 contract-data keys (archived to the hot archive if persistent, deleted if temporary) and their 1000 TTL keys, the per-ledger cap maxEntriesToArchive. A reader that derives state only from transaction meta keeps 1000 entries that no longer exist.
config upgrade settings vote
7× in this ledger
mainnet 65080525
P29 · LCM v2 · 568 txs
A validator vote changes seven Soroban network settings in one LEDGER_UPGRADE_CONFIG; the new values appear only in upgradesProcessing, not in any transaction. Fee and limit calculations that cache settings go stale here.
config upgrade frozen keys
1× in this ledger
mainnet 65273932
P29 · LCM v2 · 268 txs
CAP-0077 on mainnet: a config upgrade grows the frozen-key list from 3 to 4 accounts. Transactions touching those accounts are refused from the next ledger; the change is visible only in upgradesProcessing (config setting frozen_ledger_keys), as encoded LedgerKey bytes.
p22 refunds in tx changes after
53× in this ledger
mainnet 56085459
P22 · LCM v1 · 222 txs
Protocol 22: the Soroban fee refund is a change in txChangesAfter of each transaction, not in postTxApplyFeeProcessing as from protocol 23. LedgerCloseMeta is v1. In the public lake the TransactionMeta is v4 even at protocol 22, because Galexie sets BACKFILL_STELLAR_ASSET_EVENTS (stellar-core TransactionMeta.cpp: v4 from protocol 23 or with that flag); a default node writes v3 for the same ledger.
p12 v0 envelopes
532× in this ledger
mainnet 26588352
P12 · LCM v0 · 532 txs
Protocol 12: every envelope is ENVELOPE_TYPE_TX_V0 (a raw ed25519 source, no MuxedAccount) and LedgerCloseMeta is v0 with a classic TransactionSet. Readers written for V1 envelopes fail on backfill. The lake carries TransactionMeta v4 here as well (BACKFILL_STELLAR_ASSET_EVENTS); a default node writes v2.

On this page