DW-002 · AVAX · ● CORE · FOR FINANCE AND THE AUDITOR
A ledger that receives intent instead of guessing it.
Avax reads a stream in which every movement already knows its entity, project, counterparty and chain. Append-only, hash-chained, self-explaining.
Block height
An auditor asks what the balance was at the close. On a bank statement that is a line. On a chain it is a question about a block height — and the block height that corresponds to 23:59:59 on the last day of the month is not a fact the chain volunteers. Somebody looks it up, writes it in a spreadsheet, and everyone downstream trusts that they got it right.
It took three days to explain this to a room of auditors. They were right to be sceptical. Nothing in their training prepared them for a ledger with no statements.
Avax records the height with the balance, at the moment the period closes, in the same row. Not because it is clever, but because the alternative is a reconstruction nobody can audit twice and get the same answer.
A number a person typed once is not evidence. It is a memory with a font.
Derived or asserted
Every entry carries its provenance as a required field. There is no third state and no blank.
Derived
Follows from the address' position in the tree. No person was involved, so no person can be wrong about it.
Asserted
A person claimed it — an opening balance, a cost basis, a booking reason. Recorded with the actor, their authority, and the prior value on every edit.
What this means in the room
These four thousand entries are structurally derived. Here is the tree that proves it.
These sixty were asserted by your finance team, with these approvals.
Test those.
An auditor tests assertions. They do not need to test facts the structure guarantees. With a chain-reading sub-ledger every entry is an inference or an assertion and nobody can tell which, so the auditor tests everything.
That is not a reporting problem. It is a mathematics problem, and it is the reason the consultant gets hired.
The exception queue
Execution is never blocked; attribution is never optional. Movements that cannot be placed land in a queue that is visible, ageing and owned — and the close cannot run while it is non-empty. This is how bank reconciliation has worked for forty years.
CLOSE BLOCKED · 3 ITEMS OUTSTANDING
The pressure is applied where finance already lives. Not where treasury works.
The artifact
The auditor should not need us in the room.
The log is append-only and hash-chained; an edit is a new entry, never a replacement. Reporting is by country, not by region, because a filing is made to a jurisdiction and not to a continent. The output is meant to be handed over and read without a call.
Neither the finance team nor the auditor understands the machine, and there is no reason they should. Explaining why moving a stablecoin consumes a different coin takes an hour. Explaining why one address holds two thousand dust transfers takes another. So the explanation goes in the document:
EXCLUDED — 2,358 NETWORK-FEE TRANSACTIONS.
TRC-20 transfers consume TRX. These are not economic events.
An auditor can sign a statement that explains itself. They cannot sign one that silently filters.
Not a spreadsheet. A spreadsheet has no provenance, no lineage back to a block height, and is infinitely editable — which is precisely why an auditor cannot trust it and must test every cell. Avax produces something bank-statement legible on the surface and block-anchored underneath: the shape an auditor already trusts, with properties a spreadsheet structurally cannot have.