← all claims · /coverage
xrpl.coverage.ledger_entry_types
LedgerEntryType coverage — every type mainnet uses is listed as defined + seen or explicitly annotated
yellow
Public-infrastructure dependent OR no independent cross-check path yet. Free-tier only until Batch B walker migration lands (post-soak, ~2026-08-31) and/or an independent verification walker is wired for this series.
What this claim says
- label
- LedgerEntryType coverage — every type mainnet uses is listed as defined + seen or explicitly annotated
- page
- /coverage
- claim id (yaml)
coverage_ledger_entry_types- behavior
MONOTONIC_GROW- Layer 2 rules
- R6
- Layer 3 source
self-attested-only
Risk note
ESCROW-COPY FOUNDING CASE. Definitions come from the local rippled build's `feature`/`server_definitions` — types active on mainnet but absent from the local build silently omit (verified 2026-07-22: TokenEscrow amendment active on mainnet since 2026-02-12 with ~404 census objects; local rippled defined_entry_names has `Escrow` but no `TokenEscrow` → /coverage does not surface the type at all). 2026-07-22: declared-gap SCREAM banner shipped so the omission is loud, not silent (templates/coverage_register.html, "DECLARED GAP" block near the top). Permanent fix = node upgrade (rides Lenovo migration); banner deletes itself when rippled build ships definitions for TokenEscrow. Sibling class: the walker-scope declaration must expand every time rippled upgrades OR a new type is amendment-activated. Any diff touching the LedgerEntryType section, the coverage walker, the definitions cache, or the declared-gap banner triggers this claim.
Evidence — code paths that back this claim
- templates/coverage_register.html:182 LedgerEntryType section
- db.py:read_coverage_register_state
- db.py:read_ledger_definitions
- ledger_definitions_walker.py (6h cadence)
- coverage_register_walker.py (6h cadence)