xdrcheck conform sends every corpus entry to a driver that runs one SDK at one pinned version (a column). The driver decodes the bytes, re-encodes them and reports the values it read; the runner compares them with the entry’s expected values, which come from the bytes and never from an SDK. The public set has 21 columns; pull-request CI runs the 16 of the pr set (drivers/sets.toml).
How to read a row
One cell per entry and column, folded over the entry’s variants and conformance levels. A row of the tables below counts the cells of one column.
A divergence on your release means one of these, depending on the entry: your decoder accepts bytes stellar-core would never emit, or refuses bytes it does emit; a round trip changes the bytes; or a value your users read (an address, an amount, an ID, a map order) differs from what the ledger holds. The entry’s manifest names the finding that describes it. Not every divergence is a defect: a refusal that comes from a column’s decode profile (the Rust
limits-default limits) is declared with that profile and is the profile working as documented.
Go (go-stellar-sdk)
JavaScript (@stellar/stellar-sdk)
Python (stellar-sdk)
Rust (stellar-xdr)
stellar-core (reference column)
Divergences on the current releases
The entries where arequired column diverges: what the current release of each SDK still gets wrong. Each link goes to the entry’s row on CAP coverage. To see the cell yourself, run xdrcheck conform run --columns 'COLUMN' --entries ENTRY (commands).
go@v0.9.0:cap-0066/p22-restore-with-backfilled-restored-changes,classic/real-result-codes.testnet-5380224,strkey/api-encode-signed-payload-empty,strkey/sep-0023-v1.4.0-vectors.invalid-15,xdr-strict/api-transaction-parse-trailing-bytes.one-byte-in-final-quantum,xdr-strict/api-transaction-parse-trailing-bytes.two-bytes-in-final-quantumjs@17.4.0:cap-0021/precond-v2-min-seq-num-zero,cap-0046/scval-error-budget-exceeded-limit,cap-0046/scval-error-storage-exceeded-limit,strkey/api-encode-signed-payload-65-bytes,strkey/api-encode-signed-payload-empty,xdr-strict/api-float-union-discriminant-custom-schemarust@30.0.0:limits-default:xdr-strict/bool-value-2rust@30.0.0:limits-none:xdr-strict/bool-value-2,xdr-strict/length-prefix-exceeds-input.6h2,xdr-strict/length-prefix-exceeds-input.6h3,xdr-strict/length-prefix-exceeds-input.6h4
Three js-stellar-sdk defects, before and after their fixes
js@17.2.0, js@17.2.1 and js@17.3.0 are the releases before the fixes of three js-stellar-sdk defects (pool asset and map-key order, colliding map keys, muxed and offer IDs). Each runs on the release before its fix, which shows the declared divergence, and on the next release, which agrees (make verify-conformance OFFLINE=1). The transcripts are in evidence/js-1766/, evidence/js-1785/ and evidence/js-1789/; Known incidents lists every public incident.
Across SDK families
Whether a defect class first found in one SDK also reproduces in the others, with the versions, is on Findings.Limits
- A cell is a result on the corpus only. An SDK that agrees on every entry can still mishandle a shape the corpus does not hold.
- The matrix is a snapshot of the pinned releases at corpus version
30.0.0-dev; a newer release has no column until it is pinned inpins.toml. - The Python SDK is a community SDK; its columns run in the same way as the others.
evidence/results/conformance-matrix.json (make results-conformance); the rules are on Conformance rules and the design on Conformance.