Your file stays on your device — only its fingerprint (SHA-256) is sent, to stamp it or to look it up.
Proof of existence
Timestamp any file with @beat — free and public. Your file never leaves your device; only its SHA-256 is recorded. Later, prove the document existed at that moment.
Badge style
The badge is in the language of this page.
Preview — this is how the badge looks on your website
No script, no trackingThe badge does not connect to sigelith.org while someone reads your page — only when they click “Verify independently”.
Leaves your styles aloneThe badge has its own sealed styles: it does not change how your page looks, and your page’s styles do not change the badge.
Data written in for goodA timestamp does not change, so the date and the hash are in the code. The current state — the weekly seal, Bitcoin — is shown on the verification page.
How to paste
WordPress: the “Custom HTML” block below the file · Ghost: an HTML card · your own website: right below the link to the file.
A reader can download the file and drop it on the verification page — they will see whether it is the same file that was stamped.
Verifiable without taking our word for it
Your entry does not rest on our word. It is sealed by independent witnesses — Bitcoin, a bank and public archives — each with a different owner, country and motive. The figures are live, and every card leads to the evidence.
Public log
518
Entries in the log
Every fingerprint is chained to the one before it, and the whole log can be downloaded and recomputed by anyone.
Weekly roots and checkpoints are committed to Bitcoin through OpenTimestamps, and each checkpoint names a recent block — so the time is bounded from both sides.
Your timestamp is recorded instantly — the extra seals are added later
Right away, when you stamp: your hash, its @beat and UTC time, and its position in the append-only hash-chain. That alone already proves the document existed at that moment.
Within a day, the next daily checkpoint (after 00:00 UTC) signs the whole log — your entry included — and commits it to Bitcoin a few hours later.
After the week ends — once the current week closes (the following Monday, 00:00 UTC) its weekly Merkle root is frozen, and three independent layers are added on top:
Ed25519 signature — added the moment the week is sealed.
Bitcoin (OpenTimestamps) — submitted within the hour; confirmed in a Bitcoin block a few hours later.
Bank anchoring — the root is recorded against an independent bank reference and published, usually within a few days.
So a fresh certificate that shows “pending — week still open” is completely normal. Come back after your week has ended and been sealed, then verify again or download the certificate once more (or scan its QR code) — the signature, Bitcoin attestation and bank anchor will then appear. The timestamp itself never changes.
Weekly Hash Anchoring
Each week's Merkle root is anchored against an independent bank reference — a separate, timestamped record that the week's log existed by that date.
The root field of this entry was entered incorrectly and does not match the week's root. Entries are append-only, so it stays visible. The week's root is 955c494562039bfadb857622fffb95a9881c5250f7cd9a9479d363112c5f55dd.
Anchored by: Swissquote Bank SA (Swiss bank) · Status: ✓ confirmed · Bank ref: 1144955485
Anchored by: Swissquote Bank SA (Swiss bank) · Status: ✓ confirmed · Bank ref: 1122189662
Weeks without a single entry have no root, so there is nothing to anchor: 2026-W28.
How it works
1. Your browser computes the file's SHA-256 — the file stays on your device.
2. The hash is recorded in an append-only, hash-chained log with its @beat and UTC time.
3. Each week all hashes are combined into a Merkle root, signed with our Ed25519 key and anchored externally — against an independent bank reference and in Bitcoin via OpenTimestamps.
4. Anyone can later verify a file's hash, its timestamp, its inclusion proof up to the anchored root, the signature, and the Bitcoin attestation (downloadable .ots).
This attests existence at a point in time and integrity — not authorship or authenticity of the content.
Sharing a stamped photo through a messenger? Send it as a document/file — apps that recompress images change the bytes, and the hash of what arrives no longer matches the stamped original.
Want the exact algorithm — leaf and node hashing, the signed message, how to recompute an inclusion proof? Read the full proof specification.
Proof answers “this existed before then”. Its mirror image answers “this cannot be read until then”: a sealed capsule needs independent key holders to come together, and our key server releases its share only after the chosen @beat — so no single key holder can open it early, ourselves included. The format is open: read the capsule specification.
Weekly Merkle roots are signed with our Ed25519 key. Public key:
e7y9THJIUKvNKOZHmdBjJ8E0bOKyBFVxxMpAJ8w574Y= Key history and rotation