Every dollar that moves on the exchange leaves a row here.

How the chain is built

1. Every movement is written inside the same database transaction as the balance change. The row records seq, type, the organisation and counterparty, the amount in cents, a reference to the order, trade or payment intent, a small payload, and the timestamp. Publicly, organisations appear by their anonymous handle.
2. The row's fields are serialised to canonical JSON: keys sorted recursively, BigInt amounts as decimal strings, timestamps as ISO 8601. Two rows with the same content always produce the same bytes.
3. The hash is sha256(prevHash + canonicalJson). The first row uses a previous hash of 64 zeros.
4. Verification replays the chain from seq 1, checking that sequence numbers are contiguous, that each row's previous hash equals the prior row's hash, and that each stored hash matches its recomputed value. It reports OK or the first broken seq.

Publishing the chain head to a public network is planned and not yet live. The JSON endpoint is /api/ledger/verify.