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

# Introduction

> Istravex checks that Stellar SDKs and indexers preserve what actually happened on the ledger.

A Stellar transaction can be perfectly valid and still be misread by the software that consumes it.

Here is a real one. On 14 November 2026, mainnet ledger 65,474,279 recorded a USDC payment to the muxed account ID `1764988090084626463`. Every SDK decodes it correctly. Then a JavaScript service passes that ID through `Number()` on its way to the database, and what gets stored is `1764988090084626400`. Nothing errors and nothing logs. The payment is now credited to a customer who doesn't exist.

Istravex exists to catch that class of bug before it ships. It's a shared, versioned corpus of rare-but-valid Stellar XDR, plus the tools to run your SDK or indexer against it and see exactly where it disagrees with the ledger.

## What's in the kit

> [card] [The corpus](https://docs.istravex.com/corpus/overview.md)
>
> Real fixtures, each tied to the CAP that introduced the pattern and verified byte-for-byte against the ledger that closed it.

> [card] [SDK runners](https://docs.istravex.com/tools/sdk-runners.md)
>
> The same checks in JavaScript, Go and Rust: decode, byte-exact re-encode, and the high-level conversions where precision leaks.

> [card] [Mock RPC and replay](https://docs.istravex.com/tools/mock-rpc.md)
>
> Serve the corpus over Stellar RPC's `getLedgers` and replay it through any indexer, offline, with verdicts per record.

> [card] [istravex-lint](https://docs.istravex.com/tools/lint.md)
>
> Three Go analyzers for the ingestion mistakes that keep recurring: unvalidated memo text, unbounded recursion, fees read from the envelope.

> [card] [Hardening guide](https://docs.istravex.com/guide/overview.md)
>
> Nine rules for turning ledger data into records correctly, reviewed by a Stellar Core engineer. Every rule cites evidence.

> [card] [API](https://docs.istravex.com/api-reference/introduction.md)
>
> The corpus, canonical ledgers and every result at `api.istravex.com`, and a public replay endpoint at `rpc.istravex.com`.

## Where things stand

These numbers are generated from the repository on every build. They aren't typed by hand.

| What | Result |
| - | - |
| Fixtures | **6** across 4 CAPs (pubnet, local, testnet) |
| Provenance | **62/62** checks, byte-identical to canonical ledgers |
| SDK conformance | **54/54** checks across JavaScript, Go and Rust |
| stellar-core goldens | **15,306/15,306** LedgerCloseMeta frames round-trip in every SDK |
| Replay | naive indexer wrong on **4/4**; reference indexer right on **4/4** |
| wallet-backend pilot | **6/6** fixtures indexed correctly |
| CAP coverage | 3 of 40 XDR-changing CAPs (70 live) |

## Who it's for

* **SDK maintainers** who want proof that decode, re-encode and native conversions survive real ledger data, and who want a regression test that other SDKs share.
* **Indexer authors** (explorers, wallets, analytics, custody) who want to know whether their pipeline stores the right records for the right accounts.
* **Reviewers and auditors** who need evidence, not assurances: every result links back to a fixture, a ledger and a commit.

> [!NOTE]
>
> Istravex is proposed for the Stellar Community Fund (SCF #46, RFP 2). The kit described here is built and running; the [roadmap](https://docs.istravex.com/project/roadmap.md) shows what the grant would fund next.

## Next steps

> [card] [Quickstart](https://docs.istravex.com/quickstart.md)
>
> Run the whole kit locally in a few minutes.

> [card] [Concepts](https://docs.istravex.com/concepts.md)
>
> Fixtures, canonical ledgers, verdicts: the vocabulary used everywhere else.


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