Loading...
Loading...
Every OmegaEngine attestation is content-addressed: its id is the sha256 of the canonical document, so the artifact can't drift from the name that identifies it. Paste an id — from a badge, a document footer, or a procurement packet — and this page re-runs the issuer-signature and Merkle proof-ledger checks against the stored artifact.
Run the public sample proof path — no id needed. It fetches a deterministic attestation and verifies the content hash plus Ed25519 signature with the same npm package auditors use.
npx -y @omegaengine/verify@latest sample --api=https://omegaengine.ai
Holding an attestation id? Fetch the raw artifact and re-derive every claim offline with nothing but SHA-256 and the published Ed25519 key (no shared secret) — replace <id> with your attestation id:
curl -s https://omegaengine.ai/api/verify/<id> > attestation.json npx -y @omegaengine/verify@latest attestation.json
Issued attestations are appended to a public, append-only RFC 6962 transparency log with a signed tree head — so a proof can't be forged or backdated after the fact. Browse the log, fetch inclusion proofs, and re-check the math yourself.
Explore the transparency log →POST /api/v2/judge with "receipt": true (Pro and above) embeds meta.receipt — a portable OmegaReceipt v1, an Ed25519 signature over the canonical receipt body. Paste that JSON (or the whole response) below: this page recomputes the content hash and checks the signature against the published /.well-known/jwks.json, all in your browser. Any failed check — or a browser without Ed25519 WebCrypto — is NOT VERIFIED, with the offline fallback. Not to be confused with the server-verified DecisionProof behind GET /api/v2/receipt: that artifact only OmegaEngine can check, so it is never presented as independent verification.
Runs entirely in your browser — the receipt never leaves this page; only the public JWKS is fetched.