> ## Documentation Index
> Fetch the complete documentation index at: https://docs.xdrcheck.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Known incidents

> Public incidents in Stellar SDKs, XDR libraries and indexers, the corpus entries that hold each shape, and whether the kit reproduces it before and after the fix, runs it, checks it or holds it as input.

For maintainers of the projects listed and for anyone running them: public incidents in which a Stellar reader (stellar-core tooling, an SDK, an XDR library or an indexer) met a shape it handled wrong, the corpus entries that hold each shape, and how far this kit goes in reproducing it. Use the entries to check that your own reader does not repeat the incident.

## How to read the coverage column

| Coverage | Meaning |
| - | - |
| **reproduced** | A `make` target runs the affected project before and after its fix and shows the defect and then its absence |
| **run** | A target runs the project on the entries, and the entries declare its result |
| **checked** | A target checks the shape itself, without the affected project |
| **agreement** | Compared with a reference; not a reproduction |
| **input** | Corpus entries hold the shape; no reader of that project runs them here. Run them through your own reader |

Totals: 6 reproduced, 2 run, 1 checked, 1 agreement, 8 input.

## Incidents

| # | Project | Incident | Coverage | How | Entries | Run with | Evidence |
| - | - | - | - | - | - | - | - |
| 01 | stellar-core | `--check-lcm` goldens | agreement | not a reproduction: imported goldens equal their golden frame byte for byte, and each local-core entry that matches a golden transaction of the same shape is compared with it (only these count as mapped); for an entry that matches none, the operation tier, reported separately and not agreement of the entry, states whether every operation has a golden operation of the same shape | `*-golden.*`, `corpus/manifest/`, `corpus/mirrors.json` | `make verify-corpus` | |
| 02 | wallet-backend | CAP-73 SAC trustline | reproduced | pre-fix and fixed commits | [`cap-0073/sac-trust-creates-trustline`](https://docs.xdrcheck.dev/caps/overview#cap-73) | `make verify-replay` | `evidence/wallet-backend-731/README.md` |
| 03 | wallet-backend | CAP-40 signed-payload signer | reproduced | pre-fix and fixed commits | [`cap-0040/signed-payload-signer-added`](https://docs.xdrcheck.dev/caps/overview#cap-40) | `make verify-replay` | `evidence/wallet-backend-replay/README.md` |
| 04 | henyey | bucket-entry parse failure | input | the bucket entry and the contract-data key it failed on; no henyey reader runs here | [`cap-0085/bucket-entry-with-executable-tag`](https://docs.xdrcheck.dev/caps/overview#cap-85), [`cap-0085/contract-data-keyed-by-executable-tag`](https://docs.xdrcheck.dev/caps/overview#cap-85) | | |
| 05 | rs-stellar-xdr | VecM capacity on decode | input | length prefixes larger than the input | [`xdr-strict/length-prefix-exceeds-input.*`](https://docs.xdrcheck.dev/caps/overview#xdr-strict) | | |
| 06 | stellar-etl | data-quality sweep | input | entries for members of the sweep | [`cap-0038/claim-atoms-pool-and-order-book-mixed`](https://docs.xdrcheck.dev/caps/overview#cap-38), [`cap-0046/failed-soroban-tx-with-sac-transfers-in-diagnostics`](https://docs.xdrcheck.dev/caps/overview#cap-46), [`classic/amount-above-2-pow-53-stroops`](https://docs.xdrcheck.dev/caps/overview#classic) | | |
| 07 | stellar-etl | Protocol 28 epic | input | for the epic's XDR themes: CAP-83's `STELLAR_VALUE_EMPTY_TX_SET` and CAP-85's `CONTRACT_EXECUTABLE_EXTERNAL_REF` and `SCV_EXECUTABLE_TAG`; CAP-86 changed no XDR. The ledger entries among them replay through the stellar-etl adapter (its "Build and run" command, with `--entries`) | [`cap-0083/stellar-value-empty-tx-set`](https://docs.xdrcheck.dev/caps/overview#cap-83), [`corpus/manifest/cap-0085/`](https://docs.xdrcheck.dev/caps/overview#cap-85) | | |
| 08 | wallet-backend | AddressBytea truncation | reproduced | pre-fix and fixed commits | [`cap-0040/signed-payload-signers-1-byte-and-64-byte`](https://docs.xdrcheck.dev/caps/overview#cap-40), [`strkey/truncated-muxed-address-56-chars`](https://docs.xdrcheck.dev/caps/overview#strkey) | `make verify-replay` | `evidence/wallet-backend-replay/README.md` |
| 09 | stellar-etl | P23+ event and effect gaps | run | stellar-etl through the adapter at v2.8.34 and the pinned v2.8.35, entries declare the result | [`cap-0067/sac-mint-three-topics`](https://docs.xdrcheck.dev/caps/overview#cap-67) | `make replay-etl-known` | `evidence/stellar-etl/README.md` |
| 10 | wallet-backend | four indexer fixes | run | the commits before and after the fixes, through the replay harness and the linter | | `make lint-before-after` | `findings/REPORT-pipelines.md` |
| 11 | rs-soroban-sdk | MuxedAddress from a non-address ScVal | input | a `transfer` event whose `to` topic is a symbol; no soroban-sdk column runs it | [`cap-0067/transfer-event-with-non-address-to-topic`](https://docs.xdrcheck.dev/caps/overview#cap-67) | | |
| 12 | rs-stellar-xdr | VecM max on serde | input | | [`xdr-json/vector-longer-than-declared-max`](https://docs.xdrcheck.dev/caps/overview#xdr-json) | | |
| 13 | js-stellar-sdk | issuer and map-key order | reproduced | pre-fix and fixed tags | [`cap-0038/pool-issuers-order-by-bytes-not-strkey`](https://docs.xdrcheck.dev/caps/overview#cap-38) | `make verify-conformance` | `evidence/js-1766/README.md` |
| 14 | rs-stellar-xdr | schemas omit feature-gated types | checked | at the pinned 30.0.0, where the gates are gone: the structural walk reads the ledger against that crate's own `LedgerCloseMeta` JSON Schema and fails on an arm the schema lacks (the issue was closed as not planned) | [`cap-0088/signed-ms-local-twins`](https://docs.xdrcheck.dev/caps/overview#cap-88) | `make verify-corpus` | |
| 15 | js-stellar-sdk | colliding map keys | reproduced | pre-fix and fixed tags | [`cap-0046/scval-map-keys-collide-u32-symbol`](https://docs.xdrcheck.dev/caps/overview#cap-46) | `make verify-conformance` | `evidence/js-1789/README.md` |
| 16 | js-stellar-sdk | muxed and offer IDs | reproduced | pre-fix and fixed tags | [`cap-0027/api-muxed-account-id-encoding.*`](https://docs.xdrcheck.dev/caps/overview#cap-27), [`classic/api-offer-id-encoding.*`](https://docs.xdrcheck.dev/caps/overview#classic) | `make verify-conformance` | `evidence/js-1785/README.md` |
| 17 | js-xdr | XDR validation pass | input | of the same class: float union discriminants, a bool of 2, trailing bytes, undeclared discriminants | [`corpus/manifest/xdr-strict/`](https://docs.xdrcheck.dev/caps/overview#xdr-strict) | | |
| 18 | js-stellar-sdk | non-UTF-8 string arms | input | | [`cap-0067/to-muxed-id-text-non-utf8-memo`](https://docs.xdrcheck.dev/caps/overview#cap-67), [`classic/api-memo-text-non-utf8-roundtrip`](https://docs.xdrcheck.dev/caps/overview#classic) | | |

An entry pattern ending in `.*` names every variant entry of that ID. The **Evidence** folder holds the transcript of the run and the command that repeats it.

## Limits

* The list is the set of public incidents the repository's README names, one row each; it is not every bug ever reported against these projects.
* An **input** row proves nothing about the affected project: no reader of it runs here.

The data is `evidence/results/known-defects.json` (`make results-known-defects`); the README's table names the upstream item of each row.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.