Trust Ledger
Every computed HCS score is committed to a BLAKE3 Merkle-tree audit ledger. This makes the score tamper-evident by construction — not just by access control — meaning a customer can independently verify that a score reported for a given session hasn't been altered after the fact.
Why a Merkle tree
Altering a single historical score would change its hash, which cascades up the tree and changes the root — instantly detectable, rather than requiring a full audit to notice.
Why BLAKE3
Used consistently across CertiLayer — API keys, OTPs, and the ledger all use the same hashing primitive, chosen for its speed and modern security margin.
ℹ️
The ledger is an internal integrity mechanism today. Customer-facing proof export is on the roadmap — contact [email protected] if independent verification is a requirement for your compliance process today.