Transparency log
Every change Daryl makes, on the record.
Each receipt is hashed and appended to a public log that can only grow. Signed checkpoints let anyone confirm an entry is in the log and that nothing was removed or rewritten. The log holds hashes, never your data.
The log
Current state
No entries yet
Daryl Shield is in early access and hasn’t issued a receipt. The first one will appear here, with its index and hash, the moment it is written.
How it works
What makes it tamper-evident
- Receipts
- A signed statement of what changed: the policy before and after, the proof result, the replay result and who approved it.
- Leaves
- Each receipt’s hash is appended as a leaf. Rows can only be added; the database refuses updates and deletes.
- Checkpoints
- The log’s size and root hash are signed on a schedule, so a removed or rewritten entry would show.
- Your data
- Only hashes are public. Org and app names are hashed too, unless an owner publishes their receipts page.
Verify
Check a receipt yourself
A command-line verifier will be published with the first receipts. It will check the signature, the inclusion proof and the checkpoint without trusting us.
npx @daryl/verify receipt <id>