Oracle
make oracle: each fact's values must also appear in what stellar-core's own C++ decoder reads and in what XDRProof's schema walker reads. No SDK is involved.
make oracle # node tools/oracle.mjs
node tools/oracle.mjs --write # also record core and walker as evidence in each entryA fact is only as good as the reader that produced it. The oracle asks two readers that share no code with any SDK:
| Reader | How it runs |
|---|---|
| stellar-core | stellar-core dump-xdr, inside docker run --network none on the stellar/quickstart image pinned by digest in recipes/core-image (override with XDRPROOF_CORE_IMAGE) |
| Schema walker | tools/walker.mjs, driven only by the v30.0 XDR definitions. It rejects non-zero padding, over-length values, bad enums and trailing bytes |
For each fact, the oracle takes its expected values and checks that they appear among the values each reader produced. Enum values are checked too: tools/coverage/defs/sep0051-enum-names.json maps every XDR enum member to the string SEP-0051 prints for it, so the walker confirms a member it reached and stellar-core one its dump printed. Enum names are matched by name across all enums, anywhere in the ledger, so a common name such as success is a weak confirmation. A length fact has no value to check, and a v0-style arm name is structure, not a value. A value either reader misses is a disagreement, and the run fails. So does a ledger stellar-core cannot print: nothing in it is confirmed. With --write, it records core and walker in the fact's evidence.
A planted error must be caught
A reader that finds every value might simply accept anything. So the oracle tests itself. It takes every expected value of 10 or more digits (64-bit amounts, IDs and fees), changes its last digit and asks both readers again.
| Result | Counts as |
|---|---|
| Both readers reject the changed value | caught |
| Both readers find it: the changed value occurs elsewhere in the same ledger | a coincidence, not a failure |
| Only one reader finds it | a disagreement: the run fails |
If no planted error is caught at all, the self-test fails and the run exits 1.
What it does not check
Verify
make verify: strkey test vectors, then every entry against the schema, its hashes, a byte-for-byte round trip through native rs-stellar-xdr, the focus transaction and every fact; then every mined ledger.
Coverage
make coverage and make coverage-report: every XDR union arm reachable from LedgerCloseMeta is either reached by a corpus entry or classified with the stellar-core source line that decides it.