# Istravex

> The XDR conformance and replay kit for Stellar.

- [Introduction](https://docs.istravex.com/index.md): Istravex checks that Stellar SDKs and indexers preserve what actually happened on the ledger.
- [Quickstart](https://docs.istravex.com/quickstart.md): Run the full kit locally, then point it at your own code.
- [Concepts](https://docs.istravex.com/concepts.md): The handful of ideas everything else in Istravex is built on.
- [The corpus](https://docs.istravex.com/corpus/overview.md): What the corpus holds, where each piece comes from, and why you can trust it.
- [Fixtures](https://docs.istravex.com/corpus/fixtures.md): The six fixtures in the corpus, what each one catches, and the bug it exists for.
- [Manifest format](https://docs.istravex.com/corpus/manifest.md): Every field in a fixture's manifest.json, and the rules it follows.
- [Provenance](https://docs.istravex.com/corpus/provenance.md): How every fixture is proven byte-identical to the ledger that closed it.
- [Capturing from networks](https://docs.istravex.com/corpus/capturing.md): Pulling pinned mainnet transactions and creating fresh testnet cases.
- [Generating on stellar-core](https://docs.istravex.com/corpus/generating.md): Building fixtures on a pinned, standalone stellar-core, with no external network.
- [stellar-core goldens](https://docs.istravex.com/corpus/goldens.md): Checking every SDK against the golden LedgerCloseMeta stellar-core's own CI uses.
- [CAP coverage](https://docs.istravex.com/corpus/cap-coverage.md): Every live Core Advancement Proposal, whether it changes XDR, and which fixtures cover it.
- [Contributing a fixture](https://docs.istravex.com/corpus/contributing.md): How to add a fixture for an uncovered CAP, from finding the pattern to a green CI run.
- [SDK runners](https://docs.istravex.com/tools/sdk-runners.md): The same three checks, in JavaScript, Go and Rust, against every fixture.
- [Mock RPC](https://docs.istravex.com/tools/mock-rpc.md): Serve the corpus over Stellar RPC's wire format, so any RPC-backed indexer can replay it offline.
- [Replay](https://docs.istravex.com/tools/replay.md): Run the corpus through two indexers, one naive and one reference, and score every record.
- [istravex-lint](https://docs.istravex.com/tools/lint.md): Three Go analyzers for ingestion mistakes that keep recurring in Stellar indexers.
- [IX001 · Memo text without UTF-8 validation](https://docs.istravex.com/tools/lint/ix001.md): stellar-core accepts any 28 bytes as MEMO_TEXT. Your database might not.
- [IX002 · Recursion without a depth limit](https://docs.istravex.com/tools/lint/ix002.md): ScVal and Soroban auth trees nest. Walkers over them need a bound.
- [IX003 · Fees from the envelope](https://docs.istravex.com/tools/lint/ix003.md): The envelope says who bid. The ledger says who paid, and how much.
- [wallet-backend pilot](https://docs.istravex.com/pilots/wallet-backend.md): Running stellar/wallet-backend's own ingestion over the corpus, unmodified, and scoring what it produces.
- [Replaying into your indexer](https://docs.istravex.com/pilots/your-indexer.md): Point your own indexer at the corpus and find out what it stores.
- [Indexer hardening guide](https://docs.istravex.com/guide/overview.md): Nine rules for turning Stellar ledger data into records correctly, each one backed by evidence.
- [Review checklist](https://docs.istravex.com/guide/checklist.md): The whole guide as a code-review checklist, in any language.
- [1. Read effects from metadata, not the envelope](https://docs.istravex.com/guide/effects-from-meta.md): The envelope is a request. The metadata is the outcome.
- [2. Fees on fee-bumps and Soroban](https://docs.istravex.com/guide/fees.md): Three different numbers look like "the fee". Only one is.
- [3. Keep 64-bit integers exact](https://docs.istravex.com/guide/wide-integers.md): A double holds integers exactly up to 2^53. Stellar's IDs and amounts don't stop there.
- [4. Muxed accounts (CAP-0027)](https://docs.istravex.com/guide/muxed-accounts.md): An M… address is an account plus an ID. Keep both.
- [5. Signed-payload signers (CAP-0040)](https://docs.istravex.com/guide/signed-payload-signers.md): The payload is part of the signer's identity.
- [6. Trustlines without changeTrust (CAP-0073)](https://docs.istravex.com/guide/sac-trustlines.md): Since protocol 26, contracts can create trustlines and accounts. No classic operation is involved.
- [7. Untrusted strings](https://docs.istravex.com/guide/untrusted-strings.md): stellar-core stores bytes. Whether they're text is your problem.
- [8. Bound recursion](https://docs.istravex.com/guide/bounded-recursion.md): Decoder limits protect decoding. Your walkers need their own.
- [9. Compare only consensus data](https://docs.istravex.com/guide/consensus-data.md): Some of what's in transaction metadata was never agreed by the network.
- [API overview](https://docs.istravex.com/api-reference/introduction.md): The corpus, canonical ledgers and every kit result, over HTTP.
- [Mock Stellar RPC](https://docs.istravex.com/api-reference/rpc.md): Replay the corpus through any RPC-backed indexer at rpc.istravex.com.
- [Health](https://docs.istravex.com/api-reference/endpoint/health.md): Liveness and the build the server is running. Never cached.
- [Corpus statistics](https://docs.istravex.com/api-reference/endpoint/stats.md): The headline numbers: fixtures, SDK checks, provenance checks, golden frames, the wallet-backend pilot and CAP coverage.
- [List fixtures](https://docs.istravex.com/api-reference/endpoint/list-fixtures.md)
- [Get a fixture manifest](https://docs.istravex.com/api-reference/endpoint/get-fixture.md)
- [Download a fixture's XDR](https://docs.istravex.com/api-reference/endpoint/get-fixture-file.md): Returns one XDR value from the fixture, base64 by default (exactly as stored in the repository), or raw bytes with `encoding=binary`. `X-XDR-Type` names the XDR type and `X-Content-SHA256` is the sha256 of the decoded bytes, matching the manifest.
- [List canonical ledgers](https://docs.istravex.com/api-reference/endpoint/list-ledgers.md)
- [Download a canonical ledger](https://docs.istravex.com/api-reference/endpoint/get-ledger.md): The full `LedgerCloseMeta` a fixture was verified against, as a zstd-compressed `LedgerCloseMetaBatch` (the layout of SDF's public data lake). `X-Content-SHA256` is the sha256 of the decompressed XDR.
- [List result sets](https://docs.istravex.com/api-reference/endpoint/list-results.md)
- [Get a result set](https://docs.istravex.com/api-reference/endpoint/get-result.md): The raw output of one kit stage, exactly as committed in `corpus/results/`: SDK runs (`javascript`, `go`, `rust`), golden checks (`goldens-*`), `provenance`, `replay` and `pilot-wallet-backend`. 64-bit integers are JSON strings.
- [CAP coverage audit](https://docs.istravex.com/api-reference/endpoint/coverage.md): Every live CAP (Final or Implemented) from the pinned stellar-protocol checkout, whether it changes XDR, and which fixtures cover it.
- [Mock Stellar RPC](https://docs.istravex.com/api-reference/endpoint/rpc.md): JSON-RPC 2.0 with the wire shapes of Stellar RPC. Supports `getHealth`, `getNetwork`, `getLatestLedger` and `getLedgers` (cursor paging over the corpus's sparse ledgers). Point an RPC-backed indexer at `https://rpc.istravex.com/{network}` to replay the corpus. Batches of up to 20 requests; bodies up…
- [Self-hosting the API](https://docs.istravex.com/operations/self-hosting.md): Run the API and mock RPC yourself, as one container or straight from a checkout.
- [Production deployment](https://docs.istravex.com/operations/deployment.md): How istravex.com, api.istravex.com and rpc.istravex.com are deployed by GitHub Actions.
- [CI](https://docs.istravex.com/operations/ci.md): What runs on every push, and the templates for running Istravex in your own CI.
- [Docs](https://docs.istravex.com/operations/docs.md): How this documentation is built, kept accurate, and published to docs.istravex.com.
- [Findings](https://docs.istravex.com/project/findings.md): What building Istravex turned up about Stellar's data, its tools, and our own code.
- [Roadmap](https://docs.istravex.com/project/roadmap.md): The three proposal milestones, where each stands, and what comes after.
- [Maintenance](https://docs.istravex.com/project/maintenance.md): Who maintains Istravex, what happens on a protocol upgrade, and how to get involved.
- [FAQ](https://docs.istravex.com/project/faq.md): Short answers to the questions people ask first.
- [Changelog](https://docs.istravex.com/project/changelog.md): Releases of the kit, corpus and API.

## OpenAPI Specs

- [openapi](/api-reference/openapi.json)


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