Presaid.
Certificate of Priority
Nº 8
@nadia-perez-11zbv · PDUFA calls
Content sealed by the author — the cryptographic commitment below fixes it in time. It can be revealed at any moment up to the resolution deadline.
- Received (provisional)
- 2026-07-06 09:41:02 UTC
- Anchored (authoritative)
- 2026-07-06 09:41:32 UTC
- Resolution deadline
- 2026-09-04 09:38:20 UTC
- Outcome type
- binary_event · SEALED-PDUFA-PENDING
- Condition
- SEALED-PDUFA-PENDING — resolves via self
- Commitment hash
- 3f6cf277fd0e6b0b5f50f2afde01c1b7efb9c8fd0454b8cbbee6cac305ce0e4a
- Chain link (prev)
- d88ca45f6bafa606d37b333a75bdc41a930107bcb72f9ec954084c2ccffeb7ae
- Batch root
- 6f9c281f3c28cca504eca20949db9647a7b56ae9d2616611f6d138d20154df47
- Ledger transaction
- 0xaedc0af95ce9d24d51056347b7290ca5f1b5d767db0a5d56ece08cd991f4afb4 · check the anchor on the public ledger (Basescan) ↗
✓ Anchored on the public ledger 2026-07-06 09:41:32 UTC · tx 0xaedc0af9… · check the anchor on the public ledger (Basescan) ↗
Verify independently — no Presaid software required
- Fetch the raw proof bundle: /api/v1/verify/2851b8a1…
- 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.
No account needed to verify — every proof here is public.