Drop a receipt or evidence bundle and check it right in your browser (the Ed25519 signature, the hash-chain link, and the timestamp) using the same open verifier a regulator, auditor or customer would use. You never need an AskLedger account, and it keeps working even if AskLedger disappears. That independence is the whole point.
Nothing is sent to us. The verifier runs entirely client-side against the public key in the receipt, the same math anyone else can run.
The receipt is re-canonicalized (RFC 8785) and re-hashed. If a single field changed, even key order, the hash won't match.
The signature is checked against the signer's public key. Only the holder of the private key could have produced it.
The receipt links to its predecessor by hash (per-tenant chain), and carries an RFC 3161 timestamp you can check against a public authority.
The verifier is open source in five languages. No lock-in, no service dependency: vendor a copy and run it in your own CI if you want to.
# Verify from your terminal, nothing to install:
npx @askledger/receipts-sdk verify receipt.json
# ✓ RECEIPT VALID · canonical hash ✓ · Ed25519 ✓ · chain ✓
# Or call it from your own code:
import { verifyReceipt } from "@askledger/receipts-sdk";
const { valid, checks } = verifyReceipt(receipt, { publicKeys });
# same call in the Python, Go, Rust and Java SDKs, pick your stack.An enterprise export contains everything needed to validate on its own: the schemas, the public keys, the proofs, and the instructions. No AskLedger login, no API call, no trust in our uptime. That's what makes a receipt evidence instead of a claim, and it's why signing and verifying are, and always will be, free and unlimited.