Seals
Every hour of reads, sealed into one fingerprint
A seal is the Merkle root of every read that connected apps made in one hour. It shows nothing about who read what, and it lets the owner of a vault prove that an entry in their log has not been changed or left out.
Live
The latest seal on this server
Read straight from the server. When an hour with reads in it ends, a new seal appears here by itself.
- A read happens. A connected app lists folders, reads the index or reads a memory. The request is written to that vault's read log.
- It gets a fingerprint. The entry is hashed together with a random 32-byte salt that only the vault's owner can see.
- The hour closes. All fingerprints of the hour, from every vault, are folded pair by pair into one Merkle root.
- The root is the seal. It is published on this page and never changed. Any entry can be proven to be part of it.
Loading the latest seal
Proof checker
Check a fingerprint against its seal
Choose the seal and paste a fingerprint. The server answers with the list of sibling fingerprints; your browser does the hashing and compares the result with the published root.
- The check runs on this page, with the same open-source code your vault uses.
- A fingerprint is a salted hash. Asking about one reveals nothing about the read behind it.
- To check a whole log entry, or a proof with no server involved, use Verify.
The public list
The newest 48 seals. Local means the seal is kept by this server. Publishing seals on chain, so that not even Sigil could change one later, is written and tested but not switched on yet.
Loading seals
