Presaid.
Certificate of Priority
Nº 3
@ns-gate-178334099276 · NS
CMDTY:CL call
Revealed and awaiting its outcome — resolution deadline 2026-12-31 23:59:59 UTC. The timestamp is already proven.
- Received (provisional)
- 2026-07-06 12:29:54 UTC
- Anchored (authoritative)
- 2026-07-06 12:30:32 UTC
- Revealed
- 2026-07-06 12:29:54 UTC
- Resolution deadline
- 2026-12-31 23:59:59 UTC
- Outcome type
- price_target · CMDTY:CL
- Condition
- CMDTY:CL ≥ 1 at/before 2026-12-31 23:59:59 UTC
- Commitment hash
- 6ab7b2e049ec9b15326713d8d4818f5c2b095c06d873a658459ed91bdd25779f
- Chain link (prev)
- 1bff5792988c7b890848e0d945b7101993e3db626bacae58e6a90be850c37280
- Batch root
- 8a97132399780898c962bc51b84067665555d11b68edfb26de4494a96a61f3a7
- Ledger transaction
- 0xbd734bd94517dcbd0a7f8f3d89f7bbc9069f7ff6a52e81f4cdaf0201291d84e1 · check the anchor on the public ledger (Basescan) ↗
✓ Anchored on the public ledger 2026-07-06 12:30:32 UTC · tx 0xbd734bd9… · check the anchor on the public ledger (Basescan) ↗ — verify it yourself ▸
Verify independently — no Presaid software required
- Fetch the raw proof bundle: /api/v1/verify/5a9d6d57…
- Recompute
sha256(canonical_payload ‖ salt)and compare it with the commitment hash; fold the Merkle path to the batch root. - Read the ledger transaction above with any public RPC endpoint: its calldata is exactly the batch root, and its block timestamp is the anchored time.
Full specification: /docs/verification-spec — a reference verifier fits in ~40 lines of any language.
Don't take our word for it. Recompute the proof yourself, right here in your browser.
No account needed to verify — every proof here is public.