Skip to main content
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.
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 says how each was checked.

Topics and the guide’s sections

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 (Go code) or by hand (any language). The families are the three common mistakes and two groups beyond them.

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 gives the files; xdrlint rules the rules.