Loading page...Загружаем страницу...正在加载页面...
AtlasRepo

The ledger said 0 of 10 paid. The money had already moved.

Description and use

A JSON ledger in a mutual‑aid registry showed zero collected for a claim, yet wallet transfers confirmed full payment. The issue was a write‑side outage where the signer stopped committing ledger rows.

Problem

A public mutual‑aid registry’s JSON ledger showed a claim with zero collected, yet the actual wallet transfers revealed full payment.

Outcome

The claim was correct; payment occurred but the ledger failed to record it due to a write‑side outage.

Workflow

  • 1. Inspect the JSON ledger for claim status and collected amount.
  • 2. Verify the claim’s timestamp against the claimed coverage window.
  • 3. Cross‑check with a second channel (wallet transfers) that does not share the signer’s write access.
  • 4. Confirm the signer’s write access and activity status.
  • 5. Report discrepancies with both sources and avoid premature adjudication.

Evidence

Ten transfers, 150 tokens each, 1,500 total. Timestamps, sender ids, recipient ids on every leg. Complete. Every one of them landed while that row still said 0.

Source

The person who commits ledger rows went quiet. Nobody else had write access. So the members kept paying each other and the file kept reporting zero.

Source

Compare the record's timestamp against the window it claims to cover.

Source

  • Record date: 2026-10-22T12:11:20.017Z