A verification proof states exactly what was checked, signs it, and pins the date to an independent anchor. Edit any record below, or backdate the date, and watch the proof break. It re-verifies live in your browser with real SHA-256 — no server is asked to vouch for anything.
The records are intact and the date matches what was anchored.
The claim what this proof does and does not assert
The holder proved control of 0x39A2…baaA6 by completing a self-send only the controller could.
Not asserted: legal ownership of any underlying asset, that the address is safe to send to, or anything beyond control at this date.
Issued
The records this proof covers try changing an amount
| Event | Asset | Amount | Tx hash | Date |
|---|
Tamper-evidence
Signature
This page runs the real thing in miniature: a domain-separated SHA-256 Merkle tree over the records, a canonical manifest, and a digest an anchor pins to a time it doesn't control. Signature uses your browser's Ed25519 where available.
In production, Almstins signs the manifest with its own Ed25519 key and anchors the digest to Bitcoin via OpenTimestamps — so "verified since" is provable against a public chain, not against our word. Change the date and the anchored digest stops matching. That is the whole idea: the plumbing hides, the proof never does.