A month you can check yourself SIMULATED
Twelve thousand made-up agent payments through three made-up processors, generated in your browser from a fixed seed. The crisis data at the end is real. Everything else here is a working model of how the money would be counted, published, and checked.
1. What each processor publishes
One line per processor per month: how many payments carried the field, the total, and a Merkle root, a single fingerprint of every line in the batch, built the way Certificate Transparency logs build theirs (RFC 6962). Change any line and the root changes. Press recompute to rebuild each root from the lines in your browser.
| Batch | Payments | Total | Merkle root (SHA-256) | Check |
|---|
2. Where this month's money goes
| Crisis | Severity | Grant this month | Unmet appeal |
|---|
3. Check one owner's receipt
Pick an owner. Their receipt lists every share their agent gave. Each line comes with a short proof: the few hashes needed to climb from that line to the processor's published root. If the climb lands on the root, the line is in the total. Then try tampering with it.
| Day | Payment | Spent | Share |
|---|
A line is payment, processor, owner and share, with the share in millionths of a dollar so no rounding ever creeps in.
Don't trust this page? Download the receipt or the batches and check them with verify.py, a separate checker in Python with no dependencies: python3 verify.py receipt.json.