Skip to content
Verification playground

Don’t take our word for it.

Two instruments. On the left, create an operation and watch it move through all five stages with real cryptography in your browser. Below, load any published record and verify it yourself, or try to tamper with it.
A  /  Protocol demonstration

Process an operation.

New operation
runs locally

Use made-up values. Keys are generated in memory and discarded when you leave. Only the public record (no plaintext) is saved in this browser. Try an amount above the limit, or the DOGE asset.

Lifecycle
  1. Stage 1. Operation created

    A random operation id is assigned; nothing has left this page.

  2. Stage 2. Sensitive values encrypted

    Name, recipient, amount and memo sealed with AES-256-GCM; data key wrapped with X25519 + HKDF.

  3. Stage 3. Policy conditions evaluated

    Category, asset, mode and the amount limit checked on the plaintext, locally.

  4. Stage 4. Proof generated

    veilops-range-v1: Pedersen commitment + range proofs showing 0 ≤ amount ≤ limit.

  5. Stage 5. Verification result

    The public record is re-verified from scratch, exactly as any third party would.

B  /  Verifier

Check a record.

sample data
Public inputs
Loading…
Verification

Runs the full veilops-range-v1 verifier (both range proofs, the proof-id hash and the Ed25519 attestation). No trust in this website is needed. The same code ships in @veilops/proof-engine.

Implementation status: real cryptographic verification · proof system experimental and unaudited · records are sample data signed by a throwaway sample-operator key · no blockchain involved.