Skip to main content
The corpus is the heart of Istravex. Everything else, from the SDK runners and replay to the pilot and the linter’s calibration, exists to run code against it. It’s a directory in the repository:

What’s in it today

That’s six fixtures for four CAPs. Two of them are the same scenario on two networks: CAP-0040 and CAP-0073 each exist as a testnet capture and as a fixture generated on a pinned stellar-core. That’s deliberate. The testnet copy proves the pattern exists on a real network; the generated copy can be rebuilt by anyone, at any time, without depending on testnet (which resets).

Three ways in

Each has its own page: Capturing covers the first two, Generating the third.

Why you can trust it

A fixture is only as good as the claim that it’s real. Three things back that claim:
  1. Canonical ledgers. Every fixture’s full ledger is stored, from the most authoritative source we could get (SDF’s public data lake for mainnet), and its sha256 is recorded.
  2. Byte equality. The provenance verifier requires every XDR value in every fixture to be byte-identical to the ledger’s copy. 62 checks, all passing, on every CI run.
  3. Independent expectations. What a fixture says correct software should produce comes from Horizon or from the transaction as constructed, never from the SDKs being tested.
On top of the corpus, the SDKs are also checked against stellar-core’s own golden ledgers: 15,306 LedgerCloseMeta frames from core’s test suite.

What it doesn’t cover yet

Four CAPs is a start, not a finish. Of the 40 live CAPs that change XDR, 37 have no fixture yet. The CAP coverage page lists every one, and Contributing a fixture explains how to close a gap.