For on-chain products whose finance team reconciles by hand against a block explorer. A double-entry ledger where a balance is not spendable until it clears the chain's confirmation depth, so the books balance by construction.
Started as the accounting layer for a client's on-chain product, after their third spreadsheet reconciliation.
On-chain payments are easy to accept and hard to account for. Reorgs, variable finality, and failed-but-charged transactions leave finance teams reconciling by hand against a block explorer.
We maintain a double-entry ledger that treats chain state as an external source requiring confirmation depth before a balance is considered settled. Every on-chain event maps to a journal entry, so the books balance by construction and reconcile against the chain continuously.
It exists because we kept meeting Web3 teams whose engineering was strong and whose accounting was a spreadsheet.
A balance always carries a confirmation state. Nothing is spendable until it clears the depth policy for that chain, which makes reorg handling a configuration decision rather than an incident.
We take on a small number of engagements at a time. Bring the problem.
Free consultation