When a ledger verifies, it is consistent and its owner signed it. But it is not always the history that you saw before. An owner can sign all entries again from a given point.
ledgdex check closes this gap. It compares the ledger with the copies that it saw before, and with the receipts that other selves hold.
ledgdex check biobot orthonalyzebot https://biobot.example # one time; exit code 1 on tampering
ledgdex check biobot --every 3600 # as a worker
17 6 * * * cd /srv && ledgdex check biobot --json report.json # from cron
ledgdex workflow biobot/ledgdex.jsonl > .github/workflows/ledgdex-check.yml # each day on GitHubErrors come with signed proof in .ledgdex-check/proofs/:
- equivocation: the ledger is different from the copy that the check saw before.
- receipt_mismatch: a copy has a different entry at the position where a receipt holds a signed entry.
- ledger_changed: an address serves a different ledger.
- broken, media_changed, published_differs.
A warning tells you that the check could not check something: stale, unreachable, needs_root, receipt_bad_signer, receipt_url_mismatch, future_time, media_unavailable, behind.
Check the ledgers that you trade with each day. Example: Check shows how the check finds a rewrite.