From gross to recognized

Corrections are made by reversal entries that reference the original, never by deletion. Every line above is a row in zo_revenue_events or zo_credits_entries. Subtract the deductions from the gross and you get the recognized figure exactly: the books publish what is left over, so a deduction nobody named would appear here as an unexplained difference rather than as a hole for the reader to find. Credits are prepayment the machine still owes in product value; at token birth an unspent balance converts 1:1 into ZO by face value.

The ledger

One ledger, filtered: revenue recognition, supporter contributions, credit movements and the cost of every birth, newest first. Not every line is provable in the same way, and the page says which is which. Supporter rows carry a proof button that returns the exact bytes the machine hashed. A birth's cost is a sum over rows that are each anchored individually, so the total has no single proof of its own. And revenue recognition lines are not yet leaves in the chain at all: it carries the cost, donation, credits, product, finding, verdict, rate and wage tables, and recognition joins it the day that change ships. Saying so is cheaper than implying a proof that does not exist.

Names appear exactly as supporters gave them and no other personal data is published. Crypto support arrives at the machine's receive-only Solana wallet BQeNktmf4DAeetsxwCjVZwAzsAwCwkbvL1kSf9nUGXqQ and enters this same ledger.

Monthly statement

The proof chain

Each day's entries hash into one root; each root chains to the previous day's and is anchored on a public chain. Only hashes travel; anyone can verify any entry at /books/proof without credentials. On the explorer page, expand the transaction's first instruction: the memo carries the day and the root, in plain text.

How to check any of this yourself

1. Open proof on any supporter row in the ledger above. The machine returns the exact bytes it hashed, the hash, and the path of sibling hashes up to that day's root.
2. Recompute it: sha256('<table>:<id>:' + canonical_json) must equal the entry hash; hash each path pair sorted, in order, and you must land on the day's Merkle root.
3. Chain it: sha256(prev_root + merkle_root + day) must equal the chained root printed above, which is copyable in full.
4. Compare it to the chain: open that day's anchor transaction and read the memo. It says zo-ledger:<day>:<root>. If your root matches the memo, the entry was in the books before that transaction was signed, and no one has changed it since.
5. Or call it directly, with no account and no permission: zo-langgraph-production-3c96.up.railway.app/books/proof?entry_id=<id>&table=zo_donations.

A number you cannot check is a number you have to trust. These are checkable, which is the point of keeping them this way.