> ## 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.

# Outline and review state

> The guide's sections by topic, its checklist by mistake and how each item is checked, and how many of its claims a stellar-core or platform engineer has reviewed.

For indexer authors who want to find the part of the hardening guide that answers their question, and see how far its statements have been checked. The guide is `guide/indexer-hardening.mdx`, with its checklist `guide/checklist.mdx`; everything below is generated from those files and `guide/claims.yaml`.

> [!WARNING]
>
> **Not yet reviewed by a stellar-core or platform engineer.** Of the guide's 462 claims, 0 are confirmed or corrected, 0 disputed and 462 not yet reviewed. Each claim cites its source; [Verification report](https://docs.xdrcheck.dev/hardening/verification.md) says how each was checked.

## Topics and the guide's sections

| Topic | Guide section | Its subsections |
| - | - | - |
| Validated versus unvalidated fields, field by field | Validated versus unvalidated fields (`#validated-fields`) | How stellar-core validates a transaction; The field-by-field table; Fields that are passed through; Three places where the usual shorthand needs care; Failed transactions: what still lands in the ledger; Which parts of meta are consensus; Decoder strictness; Not yet established |
| Recommended depth and size caps | Caps (`#caps`) | Caps at a glance; Two kinds of reader; Units: decoder depth is not nesting depth; What stellar-core admits; Measured SDK defaults; Recommendations for meta readers; What to do at a bound: a trade-off; Recommendations for readers of untrusted input |
| Participants from meta, not from the envelope | Participants from meta (`#participants-from-meta`) | Deriving participants; Where envelope and meta disagree; Keep the raw XDR beside every derived value; Fail closed at protocol boundaries |
| Muxed and signed-payload handling, including the SEP-23 strkey forms | Muxed and signed-payload handling (`#muxed-and-signed-payload`) | Every SEP-23 address form; Storage widths; Muxed accounts; The event routing ID; Muxed contracts (CAP-84); Signed-payload signers (CAP-40); Decoding addresses safely; 64-bit IDs |
| A self-audit checklist: the linter's checks for indexers in any language | Checklist (`#checklist`), which points to `guide/checklist.mdx` | 35 items, below |

Field table: 66 rows, 49 validated and 17 passed through; `make verify-guide OFFLINE=1` checks it against the corpus manifest. Claims: 407 facts and 55 recommendations, each with its source.

## The checklist by mistake

Each item is checked either by [xdrlint](https://docs.xdrcheck.dev/reference/lint-rules.md) (Go code) or by hand (any language). The families are the three common mistakes and two groups beyond them.

| Family | Items | Checked by xdrlint | Checked by hand |
| - | - | - | - |
| Mistake 1: trusting fields stellar-core does not validate | 8 | 5 ([XDR101](https://docs.xdrcheck.dev/reference/lint-rules.md#xdr101), [XDR102](https://docs.xdrcheck.dev/reference/lint-rules.md#xdr102), [XDR103](https://docs.xdrcheck.dev/reference/lint-rules.md#xdr103), [XDR105](https://docs.xdrcheck.dev/reference/lint-rules.md#xdr105), [XDR403](https://docs.xdrcheck.dev/reference/lint-rules.md#xdr403)) | 3 |
| Mistake 2: no depth or size cap on recursive structures | 9 | 7 ([XDR201](https://docs.xdrcheck.dev/reference/lint-rules.md#xdr201), [XDR202](https://docs.xdrcheck.dev/reference/lint-rules.md#xdr202), [XDR203](https://docs.xdrcheck.dev/reference/lint-rules.md#xdr203), [XDR204](https://docs.xdrcheck.dev/reference/lint-rules.md#xdr204), [XDR205](https://docs.xdrcheck.dev/reference/lint-rules.md#xdr205), [XDR206](https://docs.xdrcheck.dev/reference/lint-rules.md#xdr206), [XDR207](https://docs.xdrcheck.dev/reference/lint-rules.md#xdr207)) | 2 |
| Mistake 3: participants from the envelope instead of the meta | 7 | 6 ([XDR301](https://docs.xdrcheck.dev/reference/lint-rules.md#xdr301), [XDR302](https://docs.xdrcheck.dev/reference/lint-rules.md#xdr302), [XDR303](https://docs.xdrcheck.dev/reference/lint-rules.md#xdr303), [XDR304](https://docs.xdrcheck.dev/reference/lint-rules.md#xdr304), [XDR404](https://docs.xdrcheck.dev/reference/lint-rules.md#xdr404), [XDR405](https://docs.xdrcheck.dev/reference/lint-rules.md#xdr405)) | 1 |
| Beyond the three: assumptions about the ledger's form | 4 | 1 ([XDR402](https://docs.xdrcheck.dev/reference/lint-rules.md#xdr402)) | 3 |
| Storage, versions and protocol boundaries | 7 | 2 ([XDR401](https://docs.xdrcheck.dev/reference/lint-rules.md#xdr401), [XDR406](https://docs.xdrcheck.dev/reference/lint-rules.md#xdr406)) | 5 |

## How it is kept true

* The field table is generated from `corpus/fields.yaml` joined with the corpus manifest.
* Every normative sentence carries a claim tag; `make repo-checks` fails on a sentence with "must", "never", "should" or "do not" that has none.
* The checklist is generated from the linter's rule registry, so every rule has an item.
* `make verify-guide` runs the stellar-docs repository's own format and link checks on the page, in a clone at the pinned commit.

[The guide](https://docs.xdrcheck.dev/hardening/overview.md) gives the files; [xdrlint rules](https://docs.xdrcheck.dev/reference/lint-rules.md) the rules.


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