Make a proof from your own claim

Enter a claim and the records behind it. Your browser builds a domain-separated SHA-256 Merkle tree, signs the manifest with Ed25519, and hands you a proof in the exact format Almstins uses — which you can then verify or integrate against. This is the shape of the real thing, running end to end.

This is a sandbox. The cryptography and the Bitcoin anchor are real — but signing uses a throwaway key generated in your browser, not the Almstins production key. In production the manifest is signed with Almstins' published key after control is actually verified. Here you get the format, the math, and a real Bitcoin timestamp, end to end, to integrate against.

The claim

Subject — the address the claim is about

Claim kind

Issuer name

Statement — what is (and isn't) being claimed

The records

Event, asset, amount, and date are the body. Tx hash and status are optional — include a hash when the claim is an on-chain action so a verifier can pull it off the chain themselves.

Proof built & verified

Signed and immediately re-verified in your browser — nothing was sent to a server.

What your browser did

Bitcoin anchor

Timestamp this proof's digest into a Bitcoin block via OpenTimestamps. The digest — nothing else — is sent to public calendar servers. It comes back pending and confirms in Bitcoin within ~1–2h; re-check then, or verify the .ots yourself with the standard client.

The proof

Download proof.json

Real SHA-256 Merkle + Ed25519, run entirely in your browser. The proof format matches /artifacts/proof — the same verification applies.
almstins.com/verify · almstins.com