Transparency

What Rightshold is running

Running now

• Version: 0.5.1
• Git commit: ad16ba5
• Build hash: cb83a9962ba4fe15ba7aae48750e6147749ad51960561eea59408939af7696cc (257 files)
• Witness kit SHA-256: e673093913785d32b472fa45cb60d924fc60047a3b1618c371704038fc83754b
• Signing keys: https://www.rightshold.com/.well-known/rightshold-keys.json

Deploy history

• 2026-10-29T19:15:34.061Z · commit ad16ba5 · build cb83a9962ba4fe15
• 2026-10-29T18:14:04.021Z · commit 8fb4ed6 · build 1031a26b3a73dd01
• 2026-10-29T17:58:02.051Z · commit f7b414e · build cf5d6f7d8d7ee5c0

How to check

Machine-readable: https://www.rightshold.com/v1/transparency/build. Rule changes and the 7-day waiting period: https://www.rightshold.com/transparency/changes. Verify signatures, receipts and ledger anchors offline: https://www.rightshold.com/witness/verify.

What this does not prove yet

These values are reported by the running service itself. Until builds are reproducible from a public source and attested by hardware (roadmap), a reader can check consistency over time — keys, commit and build history — but cannot independently prove the server runs exactly this code.