VERIFY · IN-BROWSER · RECEIPT CONTENTS NOT UPLOADED

Verify a signed receipt

Drop a Veritas Acta v2 signed receipt and the corresponding JWKS public key set. Receipt contents are verified locally in your browser using @noble/curves; receipt contents are not uploaded. (Static page assets load from this CDN; the optional "Load example" button fetches from a public jsDelivr mirror.) Apache-2.0

Drop receipt.json

or paste the JSON below

Drop jwks.json

or paste the JSON below

What this verifies. Ed25519 signature over the RFC 8785 (JCS) canonical encoding of the receipt payload, against the public key matched by kid from the JWKS. Same algorithm and parameters as @veritasacta/verify on npm.

What this does not verify. That the issuer is who they claim to be (JWKS trust is your responsibility). That the data committed in the payload is true (only that whoever holds the private key signed it). That the algorithm is fair, truthful, or beneficial — receipts are an evidence primitive, not a compliance certification.

Format spec. draft-farley-acta-signed-receipts (IETF). Worked example: VeritasActa/x-algorithm-receipts.