Public transparency log
Every custody event in BoC is appended to a public, append-only Merkle log (RFC 6962, the same construction as Certificate Transparency). Each leaf commits only opaque hashes — no file content, no personal data. Periodic Signed Tree Heads are published and anchored, so anyone can prove a record's event is in the log and prove the log was never rewritten or forked.
Latest signed tree head
- Tree size
- 36 leaf(s)
- Root hash
- 3f9b11dcd83c02b7bdbf6d815ecf8434f330239c11e86ea16d72b38b260425e5
- Published
- 2026-06-30T19:40:17.836Z
- Notary signature
- 3fadc92f204aa6e438f246038c6ba5128588f29c1e16c44b6be619b2b54b0553297608fe51d36cf6171b81ef113a8714a5c64cb25248d35e140658ebdd234503
- On-chain
- local Ed25519 attestation (no chain configured)
- Witness co-signatures
- 1 co-signature(s)
Verification & trust model
- Signing keys
- 1 key(s) in the endorsement chain (from the genesis identity)
- Witness key
- 94700e463e2e6239e0fc8f96c6454282e466a7a1d77e207e4c47e4843b8bd5db
- Monitor
- no incidents — last verified size 36 at 2026-08-01T16:53:56.058Z
The witness co-signs each tree head after checking append-only consistency, and the monitor re-checks the log. Honest scope: by default the signing key, the witness, and the monitor are all operated by BoC (the witness runs in-process unless an external BOC_WITNESS_KEY is deployed on a separate host), so an empty incident list / a valid co-signature is BoC vouching for itself — it constrains accidental corruption and outside attackers, NOT a dishonest operator. Operator-independent verification of append-only-ness requires either a tree head you (or a third party) retained earlier out-of-band to compare, or an on-chain anchor of the root (not configured here). See /api/log/keys and /api/log/monitor.
Verify it yourself
These endpoints return JSON; verify the proofs offline against the notary public key (see the proof bundle's notary.ed25519PublicKey).
- /api/log/sth — the latest signed tree head (or ?size=N)
- /api/log/proof?event=<eventHash> — inclusion proof for a custody event
- /api/log/consistency?first=N&second=M — append-only proof between two tree heads
- /api/log/entries — public leaf listing (hashes only)
Prefer a tool? Download the standalone offline verifier (zero dependencies) and run node verify-bundle.mjs bundle.json.