Skip to main content
Every version below is from pins.toml. xdrcheck pins check fails when a version is named anywhere else or a constant in the code differs from it.

Reference table

Notes per component

stellar-core as a generator. The generator runs the pinned release binary with RUN_STANDALONE=true, MANUAL_CLOSE=true, no peers, and METADATA_OUTPUT_STREAM to a file; it submits with tx?blob=, arms upgrades with upgrades, closes with manualclose, and reads LedgerCloseMeta records from the stream. No change to stellar-core is needed. stellar-core as a decoder. The core@30.0.0 column shows how core decodes bytes (L0 only), not what core admits to the network. Negative entries record what core does with the input in core_behaviour. XDR versions in the corpus. LedgerCloseMeta v0, v1, v2; TransactionMeta v2, v3, v4. Each ledger variant records both versions, the meta flags that change what is emitted (EMIT_CLASSIC_EVENTS, BACKFILL_STELLAR_ASSET_EVENTS, ENABLE_SOROBAN_DIAGNOSTIC_EVENTS, the Soroban meta extension) and a profile: lake, golden-test (one named core test’s flags) or custom. Passphrases. network names the passphrase, not the origin: a local standalone chain on the mainnet passphrase is pubnet with source.kind: local-core. Testnet resets. Testnet history objects are vendored with their epoch and marked perishable; xdrcheck-corpus refetch checks every vendored object against the lake. The next reset (2026-12-16) is a dated event in pins.toml. Defects found. Divergences the runs find in these components are reported to the project that owns them, and declared on the corpus entry that shows them, so the next run checks the fix. Lists: Results.