Receipt anchors
Each night, when anchoring is on, new check receipts are folded into one SHA-256 Merkle root and that root is submitted to public OpenTimestamps calendars. A pending anchor is a calendar submission, not a Bitcoin confirmation.
Anchors
| Date | Merkle root | Receipts | Status | Proof |
|---|---|---|---|---|
e3bd11c2fa9e818a66c1fa322586612e28ceb6027155c84136198a2c4cac08de | 2000 | pending. Not a Bitcoin confirmation. | an-1063df4cc4c91307.bin.ots |
JSON: /anchors.json. One receipt's path: /v1/receipts/<id>/proof.
Check a root with ots verify
The .ots file is a detached OpenTimestamps proof of the 32-byte merkle root (raw bytes, not the hex text). Save that file as <id>.bin and the proof as <id>.bin.ots, then run: ots verify <id>.bin.ots. While the status is pending, ots upgrade <id>.bin.ots asks the calendars again. Pending is not a Bitcoin confirmation.
status pending means the digest was submitted to OpenTimestamps calendars. It is not a Bitcoin confirmation. status confirmed means the .ots proof contains a Bitcoin block header attestation. ots verify checks that attestation against Bitcoin. This service does not re-query Bitcoin.
Leaf hash is SHA-256 of a 0x00 byte followed by the UTF-8 RFC 8785 (JCS) JSON of the anchored receipt. A signed receipt is anchored as its signed view (the public receipt, including kid and signature). An unsigned receipt is anchored as the stored JSON body. Parent hash is SHA-256 of a 0x01 byte, the left child, and the right child. An odd node with no sibling is carried up unchanged. Receipt order is created_at ascending, then id ascending.
Calendars: https://a.pool.opentimestamps.org, https://b.pool.opentimestamps.org. They aggregate digests and pay the Bitcoin transaction. This service does not create one.
Docs: receipt anchors.