We verify on-chain claims independently.
When a project says its reserves are backed, its payouts are bounded, or its code cannot overspend, we re-derive that from raw ledger data and publish what could and could not be proven.
What that means in practice
- Every figure is recomputed from the ledger, never taken from a dashboard, an export or the counterparty's own report.
- Results are pinned to a specific ledger index and cross-checked against more than one independent node. Disagreement between nodes is reported, not smoothed over.
- Anything we could not establish is written down as unproven. Absence of a finding is never presented as a clean result.
What we do
Hook review
A Xahau Hook read line by line against the behaviour you state it has. Findings, a testnet reproduction wherever one is possible, and residual risk stated plainly. The report reaches you unedited.
Independent verification and certification
Your stated properties proved against every input the prover reaches, a testnet reproduction, and a certificate carrying the evidence behind it rather than an assertion.
Proof of reserves and supply consistency
Holdings re-derived from raw chain data across at least two independent sources, fail-closed, pinned to a ledger. Attribution is reported separately from balance, because a gap in one is not a shortfall in the other.
What we will not do
We do not issue a certificate for something we could not verify. We do not soften findings, and we do not remove them at a client's request. Where something needs a chain to settle it and the chain cannot, we say it is unverified rather than dress it up.
A worked example
In July 2026 we certified a Ward Protocol lending lifecycle on XRPL Devnet: nine semantic checks recomputed from the chain, one residual disclosed.
Re-deriving a later Ward certificate in September, we found a stale reserve constant in our own issuing script. The published ratio was wrong; the verdict was not. That is recorded beside the certificate, and Ward was told.
Devnet later purged the pinned ledger. That certificate can no longer be reproduced by anyone, including us, and Ward publishes it on their own site marked exactly that way.
A certificate that quietly stops being checkable is worth less than one that tells you it has. We would rather ship the second kind.
Three certificates issued to date. Two remain reproducible today.
Kairo Vault Technologies GK · 合同会社 Kairo Vault Technologies
Corporate number 8010003051230 · Tokyo, Japan
Enquiries: dane@kairovault.com
Entity details: for-banks.html