On the
record.

Every key change, hash-chained. Every checkpoint, externally anchored. Verifiable without trusting us.

01 · The log

Every key, chained.

Every device key registration, revocation, and verification — written to a tamper-evident log with cryptographic links.

391
log entries — recorded key events
83
devices tracked with encrypted access
25/25
device chains verified — recomputed hashes
Report generated.

2026-10-15 09:36:13 UTC

Log Fingerprint
ExCfGzdjrYBtHiGaGRqrzqTb••••••••8kmSw_576XDA

SHA-256 over all 391 entry hashes. Changes if any entry is added, removed, or altered.

Integrity Check
All chains intact.

A sample of 25 device chains was verified by recomputing every hash. If a chain breaks, key operations are blocked until resolved.

Key Activity
Keys registered
84
Keys revoked
51
Keys verified
256
02 · How it works

Verifiable by construction.

Three properties that make the log trustworthy without trusting us.

01

Tamper-evident.

Each entry is linked to the previous one by a cryptographic hash. Any modification breaks the chain and is detectable on verification.

02

Self-verifying.

The chain is recomputed on every key operation. If a single hash does not match, the operation is blocked.

03

Externally anchored.

Periodic signed checkpoints are submitted to an independent timestamping service, so completeness can be verified without trusting R1's internal consistency.

Hire(d) better.