Trust anchory6F3rt10CEcSakCr…· ed25519
● chain ok32 entries

OpenTimestamps anchors

Bitcoin time-attestation history · 2 anchor events · 2 confirmed in Bitcoin

Anchor cadence

~5 min

cron-driven · idempotent within cooldown

Confirmation time

~1 h

Bitcoin commit + 6 confirmations

Latest anchor

12mo ago

block 893,222

Total anchored entries

32

every entry covered by ≥ 1 anchor

Anchor timeline

paysafeanchor #2● confirmed

Head hash (SHA-256)

d1ec79ea79623e8c48405f0fd9ae78b4…

Bitcoin block

893,222

Entry count covered

3 entries

Anchored at

2025-05-12T11:40:00.000Z

Verify against any Bitcoin full node

ots verify paysafe-runtime-ai-receipts.jsonl.anchors/d1ec79ea79623e8c….ots
paysafeanchor #1● confirmed

Head hash (SHA-256)

8373504dccaa9e118977e420769f33ed…

Bitcoin block

893,221

Entry count covered

1 entry

Anchored at

2025-05-12T11:35:00.000Z

Verify against any Bitcoin full node

ots verify paysafe-runtime-ai-receipts.jsonl.anchors/8373504dccaa9e11….ots

How OpenTimestamps anchoring works

  1. Every ~5 minutes, the substrate's cron computes the current L12 HEAD hash for each chain.
  2. The hash is submitted to OpenTimestamps calendar servers (alice.btc.calendar.opentimestamps.org and peers). Calendars aggregate submissions into a Merkle tree.
  3. Within ~1 hour, the Merkle root is committed to Bitcoin as one transaction. Subsequent OTS upgrade calls add the Bitcoin path to the local .ots proof file.
  4. After 6 confirmations (~1 hour additional), the proof is "complete" — verifiable offline against any Bitcoin full node, no calendar trust required.

Backdating past the most recent anchor block becomes provably impossible — that's the property regulators care about.