★ Public verifier · no login required

Verify a4 Qubitsattestation

Drop any attestation JSON below. The Merkle inclusion proof is recomputed in your browser per RFC 6962 §2.1.1 and cross-checked against the published root on trust.4qubits.com. Tamper-evident, regulator-shareable, and zero trust in this page.

Drop a 4Qubits attestation JSON

or click to browse — Merkle proof + ML-DSA-87 signature run entirely in your browser

Or fetch a fresh receipt from the ledger

Pulls the attestation packet directly from /v1/{tenant}/ledger/attestation/{entry_id}. The endpoint is tenant-authenticated, so paste a token to fetch your own entry. The packet is still verified entirely in your browser below.

API baseTenantEntry IDBearer token (operator only — never required for drag-drop)

Or paste raw JSON

Append-only proof · SEC Rule 17a-4(f) WORM

Verify the ledger is append-only between two checkpoints

An inclusion proof shows a single entry exists. A consistency proof shows the ledger between two checkpoints has not been rewritten, reordered, or had entries removed — the cryptographic WORM requirement. Math runs in your browser.

Drop a consistency-proof JSON

Schema: { old_root, old_size, new_root, new_size, proof_hashes }

Or paste raw JSON

Step 1

Drop the JSON

Anything Attest exports — a single ledger entry, an evidence bundle, or a board-ready packet.

Step 2

Recompute the Merkle root

Your browser walks the audit path and rebuilds the root locally. The portal can't lie about this; you don't need to trust it.

Step 3

Cross-check + verify ML-DSA-87

The recomputed root is matched against the per-tenant published root, then the ML-DSA-87 (FIPS 204) signature is verified in your browser via @noble/post-quantum. No backend trust required.