Signed Receipt Builder (Ed25519)

Canonicalize JSON → SHA-256 hash → sign/verify (client-side). No uploads.

1) Payload → Canonical → Hash

If payload is valid JSON, we canonicalize by sorting object keys recursively. Otherwise, we sign the raw text bytes.

Payload (text or JSON)

Canonical (what gets signed) SHA-256 (hex)

Keys stay in your browser memory. You can export the public key; keep the private key safe.

Public key (raw, base64) Signature (base64) Paste-ready receipt

Receipt format

You can cite this in posts/issues:

receipt:v1 alg=Ed25519 hash=sha256:<hex> pubkey:b64=<...> sig:b64=<...>