About this page

Demo guide — how to read the live proof

Almstins Verify turns a claim into a proof you can check yourself. This demo runs that proof live in your browser: edit the underlying data or change the date, and watch the proof reject the change the instant you do. It never asks a server to vouch for anything, so you are not trusting Almstins. You are checking the proof on your own machine.

What this is

You are looking at the real thing in miniature. Nothing to install, no account, no login. Your internet connection only loads the fonts. The proof logic itself runs entirely on your device. Close the tab and nothing was sent anywhere.

What you are looking at

The claim. States exactly what the proof asserts (control of a receiving address) and, just as importantly, what it does not (not legal ownership of any asset, not that the address is safe). A proof here is never a blanket "verified."
The records. The events the proof covers. Every field is editable.
Merkle root. A single fingerprint of all the records together. Change any one record and it changes.
Signed manifest digest. A fingerprint of the whole proof (claim, issuer, date, records), which is what gets signed and anchored.
Anchor. The digest pinned to an independent timestamp, so the date cannot be moved after the fact.
The banner. Verified (green) or Tampered (red). It updates live as you edit.

Try it — three moves

Change an amount in any record (or click "Tamper a record"). The banner turns red: the Merkle root shifted, so the signed digest no longer matches what was anchored. Any change to the data is caught.
Click "Backdate the date." Red again: the "verified since" date cannot be moved without breaking the anchor. The date is pinned to independent time, not merely asserted.
Click "Reset" to return to Verified. ("Re-issue proof" makes a fresh, honest proof of whatever the current state is. You can always make a true new proof; you simply cannot forge the old one.)

Why it matters

You check it yourself. Verification runs in the reader's browser, so trust does not route through Almstins. A counterparty confirms the proof independently, without taking anyone's word.

It never overclaims. The proof states its exact scope, which is precisely why "verified" can be relied on: the system withholds the word when it must.

What is real, and what production adds

This demo uses real SHA-256 hashing and your browser's Ed25519 signatures. In production, Almstins signs the manifest with its own Ed25519 key and anchors the digest to Bitcoin through OpenTimestamps, so "verified since" is provable against a public blockchain rather than against anyone's word.

That is the whole idea: the plumbing hides, the proof never does.

Open the live demo Visit Almstins

Runs in any modern browser·no login·no data leaves your device