Skip to main content
For SDK maintainers and indexer authors meeting the corpus for the first time. After this page you can read any entry’s manifest and check its bytes and expected values yourself (xdrcheck entry <id>, --decoded for the XDR-JSON). Every corpus entry is one JSON manifest under corpus/manifest/ plus the XDR files it names. This page walks one real entry, cap-0040/extra-signer-signed-payload-local (CAP-40), field by field. The format of every field is on Manifest and index format; the JSON Schema is corpus/schema/manifest-entry.schema.json.

What the entry is

Where the bytes come from: both passphrases

The entry has 4 variants: the same scenario step run on a local, offline stellar-core under the testnet and the mainnet passphrase, at two protocols. The network ID is part of every transaction hash, so the hashes differ by passphrase while the accounts, derived from public labels, are the same. Each variant’s source records the stellar-core that emitted it (30.0.0, commit 0e49751aa9dd, and the sha256 of its package and binary), the scenario file (corpus/scenarios/s02-signed-payload-and-signers.yaml), the step (extra-signer-in-preconditions) and its hashes, so make verify-generate can run the scenario again offline and compare. reproducibility: normalised-identical says how the regenerated bytes compare.

What a correct reader must produce

expect holds the values a correct reader derives from the ledger. xdrcheck-corpus verify checks each pinpointed value against the decoded bytes and requires the reference extractor, which derives participants and movements from what stellar-core changed, to agree with the rest (Manifest, section 6). The same expect holds for every variant; ${derived.…} stands for a per-variant value such as the transaction hash. participants.exact and movements_exact are true: a reader that records any other participant or movement fails the entry. The replay harness compares an indexer’s stored rows with these values (Replay).

Check it yourself

Decode and re-encode every variant byte for byte through rs-stellar-xdr, check the hashes, and compare with the decoded values (after make build):
Or read the files with nothing but Python 3 (and the zstd command for the decoded sidecar):

What the kit’s runs say about it

  • SDK conformance: agrees in 21 of 21 columns (SDK matrix).
  • Replay: baseline 0.1.0 on sep54-dir: pass; wallet-backend f0c00cf52420 on rpc: pass; wallet-backend f0c00cf52420 on sep54-s3: pass (Replay results).
  • Mainnet: its rarest shape token occurs 81 times on pubnet, first at ledger 41,573,647 and last at 65,288,361 (Mainnet scan).