Public ledger PILOT
Records stay private. Their fingerprints are public. Each private record is encrypted by its owner and kept in the owner's own storage. Only a one-way SHA-256 fingerprint goes into this public, append-only log, so nobody can read a record from the log, but anyone holding the record can prove it was logged and has not changed since.
Merkle root: f74185b4ac5fa389b0872a26d19edfbcbdfb8cf850adaed73e48e6873658ea58
Chain head: 2c5283e9fbffbfc65882def5e394dda804a84656f86dd06d24ec7be2ac5ad143
As of 2026-11-01 08:39:21 UTC. Machine-readable: /ledger/api/head · /ledger/api/log/1
Check a record
Paste the record's fingerprint, or paste the record text and its salt to compute the fingerprint here in your browser. Nothing you type is sent except the fingerprint.
Or compute it from the record text and salt
Latest entries
| # | Leaf fingerprint | Logged | Chain | |
|---|---|---|---|---|
| 5 | db1533a5ff36ae66b66507ca9ac03514329aac3a78836f5b73ca861bb28fe395 | 2026-11-01 08:11:49 UTC | 2c5283e9fbffbfc6… | |
| 4 | 4f30f46388888c78b8bb1d895bf461101d74962c40bf31b73de05e6dd56271dd | 2026-11-01 07:37:50 UTC | 78fb696ab6ca63a1… | TEST, disabled |
| 3 | fc31ad11eada5d8ca95a3093b8f9668ad962387223de4d99cc6c4645a1b99860 | 2026-11-01 06:58:49 UTC | 0f410d9d3ec9353a… | TEST, disabled |
| 2 | 96c290f09ae0ca015f9c99d7348d02f11858052d968998283b9519b6f9eaeddb | 2026-11-01 06:58:49 UTC | 4c1fb82218757411… | TEST, disabled |
| 1 | 8c6b727894129d4a0f59120dc191874b4fed037e18fe64bb22747855afddc9d8 | 2026-11-01 06:58:49 UTC | f901a34a33d7b151… | TEST, disabled |
How it works
1. The owner computes record_hash = SHA-256(salt + newline + record). The random salt stops anyone from guessing short records.
2. The log stores leaf = SHA-256("AL-LEDGER-LEAF-v1" + newline + record_hash), links it to the previous entry in a hash chain, and adds it to a Merkle tree (the RFC 6962 layout used by Certificate Transparency).
3. A check returns an inclusion proof. This page recomputes the Merkle root from that proof in your browser, so you don't have to trust the server's yes or no.
4. Entries are never edited or removed. Test entries are labeled TEST and switched off, not erased.
5. Once a day the log's size, Merkle root and chain head are written into a short snapshot, signed with the ledger's Ed25519 key, and its SHA-256 fingerprint is sent to free OpenTimestamps calendars. Those calendars fold it into a Bitcoin transaction, so after about a day anyone can prove the snapshot existed by then, without trusting this site.
Pilot status: runs on albertlane.net infrastructure. Signed snapshots and OpenTimestamps proofs are live (phase 2). No wallets, keys for funds, or money are involved, and nothing is spent on any blockchain. No certification is claimed. ledger-pilot-2 (t1049).
Signed daily snapshots
| # | Day (UTC) | Size | Outside timestamp |
|---|---|---|---|
| 2 | 2026-11-01 verify · message · .ots | 4 | submitted to 4 calendar(s), waiting for Bitcoin confirmation (normal for the first day) |
| 1 | TEST-2026-11-01T07:37:49Z TEST, disabled verify · message · .ots | 3 | stamped by the backup path, waiting for Bitcoin confirmation (normal for the first day) |
Signing key (Ed25519, key id d9eb6b5d0eea5b6c):
0bd4498a965fdd5a9df379ad37ef4b1ce66eead35cdac21b5d7620274a50b65e
/ledger/api/pubkey · /ledger/api/snapshots
Security events
Blocked and refused requests against this site are published as they happen, with no raw IP addresses or emails. Open the public security log.
© Albert Lane. All Rights Reserved. Albert Lane Proprietary Software License. albertlane.net