Key Transparency

Every key change.
On the record.

Every time a device key is registered, revoked, or verified in R1, it is written to a tamper-evident log with cryptographic links between entries. This page provides a live summary of that log.

Log Entries
217
Recorded key events
Devices Tracked
53
With encrypted access
Report Time
2026-08-30
23:33:05 UTC
Log Fingerprint
0XAEzRa8AQOgoV_BZe2VFiEj••••••••2msUmiMbfMEY

SHA-256 over all 217 entry hashes in the log. Changes if any entry is added, removed, or altered.

Integrity Check
25/25device chains verified

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

Key Activity
Keys registered
53
Keys revoked
33
Keys verified
131

How this works

Tamper-evident

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

Self-verifying

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

Externally anchored

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