Proofs PREVIEW
Checking a record against something outside the system that wrote it.
What it is
- Audit events are batched into a Merkle tree and the root is anchored on the Bengar chain. A proof shows an event is under a root a witness independently holds.
Why it exists
- An audit trail held by the party being audited is a claim. Anchoring makes it checkable by somebody who does not trust that party.
How it works
- Fetch the proof for an event.
- Verify the path to the root.
- Ask a chain node whether it holds that root at that height.
Who uses it
- Auditors
- Regulated customers
- Anybody who has to prove a negative later
Security boundary
- Four outcomes: VERIFIED, INVALID, NOT_WITNESSED, UNAVAILABLE — and they are not three.
- “We could not look” is never reported as “we looked and it was wrong”.
Example flow
Six months later
- A reviewer asks about a transfer from March.
- The audit event is fetched with its inclusion proof.
- The root is confirmed at the anchored height by a node the reviewer chooses.
- VERIFIED — the record has not been edited since it was anchored.
Current status
| Capability | Status | Where |
|---|---|---|
| Verify an audit event against its anchor | AVAILABLE | /projects/:id/proofs |
Related API
GET /v1/projects/:id/audit/:auditId/proofPOST /v1/console/projects/:id/proofs/verify