Receipt
SignedPackage id—
Signed at—
Domain—
Jurisdictions—
Risk tier—
Warranted actions—
Regimes cited—
Compliance gaps—
Trace sha256—
PDF sha256—
Signer key id—
Public key—
Signature—
Bitcoin anchor—
OTS receiptDownload .ots receipt → verify offline with
ots verifyWhy is the Bitcoin anchor pending?
OpenTimestamps is a four-stage protocol with 30-90 min total latency, by design:
1. Submit · the SHA-256 went to three calendar servers (a/b pool + finney). Done at sign time.
2. Calendar batches · calendars batch hashes into a Merkle tree and write the root into a Bitcoin transaction. 1-60 min.
3. Bitcoin block · the transaction is mined into a block. ~10-60 min average.
4. Confirmations · six blocks of confirmation before the calendar serves the upgraded receipt. ~60 min more.
This page auto-upgrades the receipt every 30 min via a background worker. The "WARNING" any external verifier shows right now is the protocol working as intended — no party (not even Warrant) can shortcut Bitcoin's proof-of-work timing.
1. Submit · the SHA-256 went to three calendar servers (a/b pool + finney). Done at sign time.
2. Calendar batches · calendars batch hashes into a Merkle tree and write the root into a Bitcoin transaction. 1-60 min.
3. Bitcoin block · the transaction is mined into a block. ~10-60 min average.
4. Confirmations · six blocks of confirmation before the calendar serves the upgraded receipt. ~60 min more.
This page auto-upgrades the receipt every 30 min via a background worker. The "WARNING" any external verifier shows right now is the protocol working as intended — no party (not even Warrant) can shortcut Bitcoin's proof-of-work timing.
The signing key fingerprint is published at /.well-known/warrant-keys. Anyone — including the regulator — can verify the artefact's signature locally without contacting Warrant. OpenTimestamps anchoring proves the document existed at a specific Bitcoin block height; confirmation typically lands within ~60 minutes.