Bitcoin Anchors · OP_RETURN · Public Receipts

Public Anchoring Receipts (Hash-Only)

This page lists representative Bitcoin mainnet anchors and explains how to independently verify that a disclosed state existed at a given time. Anchors are hash-only: no raw evidence, filenames, or PHI are written to the chain.

For the current public deployment record, see Docs (including Ordinal 15). For Stage IV anchoring receipts, the complete list is published as ANCHOR_INDEX_StageIV.ndjson.

SENTINEL schema: SENTINEL|SESSION|<ripemd160>|<sha8>Hash-only · zero custody · publicly verifiable

How to verify an anchor

Identify the TXID and payload from the table below (or from the Stage IV index).
Open a public explorer (e.g. mempool.space).
Paste the TXID and confirm the OP_RETURN output matches the payload.
Independently recompute digests from the frozen source artefact and confirm parity with the payload fields (sha8 and ripemd160).

For verification scope and claim boundaries, see Documentation.

Stage IV (QMSv5) — Representative anchors (see full index)

Stage IV anchors are published as a complete NDJSON index in the repository provenance directory. This table shows representative entries only.

Run / Label	Meta ID	TXID	Block	Payload
Stage IV (Node 02) — Anchor example Representative entry. Full list is in ANCHOR_INDEX_StageIV.ndjson.	Node2_IV001	`f84bff85…be9f2d` mempool.space →blockstream.info →	927934	`SENTINEL\|SESSION\|d7382d3648f25121177ec851115bb94…`
Stage IV (Node 03) — Anchor example Representative entry. Full list is in ANCHOR_INDEX_StageIV.ndjson.	Node03_IV045	`f08e329c…b3a3a4` mempool.space →blockstream.info →	932560	`SENTINEL\|SESSION\|9f64d6cfedc9524fe9683b1b472a7c2…`

Full Stage IV index: ANCHOR_INDEX_StageIV.ndjson.

Ordinals (Context) — Selected entries

Ordinals listed here are historical context entries. The active public deployment record and disclosure integrity artefacts are in Docs (Ordinal 15).

Run / Label	Meta ID	TXID	Block	Payload
Ordinal 11 (Context)	ORDINAL11	`a09523a5…7a1540` mempool.space →blockstream.info →	921107	`ORDINAL11\|b0c8b2223eab705cac6bf7801b64945f7ed470…`
Ordinal 12 (Context)	ORDINAL12	`e3dd84f7…fae326` mempool.space →blockstream.info →	921121	`ORDINAL12\|fb1822a8113a1b691a7ef64bb7cd64ea2fa02b…`
Ordinal 13 (Context)	ORDINAL13	`66cd04d7…1fb991` mempool.space →blockstream.info →	923689	`ORDINAL13\|dd498abe7b95b3faade9b244401a4f68756e82…`

Stage I (Context)

These anchors are provided as historical execution lineage context only.

Run / Label	Meta ID	TXID	Block	Payload
RUN001 – Amplify Stress Test (Context)	Sentinel.QMS.v4.Amplify.REPRODUCIBILITY.001	`3e9a4db0…4792c4` mempool.space →blockstream.info →	923818	`SENTINEL\|SESSION\|ddbdb990cd4b0dc81439574184da367…`
RUN002 – Amplify Stress Test (Context)	Sentinel.QMS.v4.Amplify.REPRODUCIBILITY.005	`9c2eb239…05d156` mempool.space →blockstream.info →	923939	`SENTINEL\|SESSION\|99d34e624d3c105aec61a35dfefae71…`

Stage II (Context)

These anchors are provided as historical execution lineage context only.

Run / Label	Meta ID	TXID	Block	Payload
RUN003 – Deterministic Re-Audit (Context)	Sentinel.QMS.v4.Amplify.REPRODUCIBILITY.009	`9721d684…6af8f7` mempool.space →blockstream.info →	924058	`SENTINEL\|SESSION\|be31ff46db2b5ddc4fdbe2f299d38f0…`
RUN004 – Deterministic Re-Audit (Context)	Sentinel.QMS.v4.Amplify.REPRODUCIBILITY.013	`4873e651…793e9e` mempool.space →blockstream.info →	924061	`SENTINEL\|SESSION\|98404a94fb61ef21f1277f499fa7130…`

Stage IIIA (Context)

These anchors are provided as historical execution lineage context only.

Run / Label	Meta ID	TXID	Block	Payload
RUN005 – Tamper Challenge Plan (Context)	Sentinel.QMS.v4.Amplify.REPRODUCIBILITY.017	`d1d78c40…007682` mempool.space →blockstream.info →	924781	`SENTINEL\|SESSION\|47c4d5159a6a62eb80096c8b73e3c7f…`
RUN009 – Tamper Challenge Result (Context)	Sentinel.QMS.v4.Amplify.REPRODUCIBILITY.033	`9de8e1d1…111d73` mempool.space →blockstream.info →	924793	`SENTINEL\|SESSION\|0521313f7fc323d51fb68f2134974ac…`

Stage IIIB (Context)

These anchors are provided as historical execution lineage context only.

Run / Label	Meta ID	TXID	Block	Payload
Multi-Entity Baseline Corpus (Context)	Sentinel.QMS.v4.MultiEntityAnchor.001	`6e3f0744…1c3e7f` mempool.space →blockstream.info →	925073	`SENTINEL\|SESSION\|158fdb62a83f78bd48017266bb82667…`
RUN010 – MULTI_BASELINE (Context)	Sentinel.QMS.v4.Amplify.REPRODUCIBILITY.037	`5b0fdf19…54dce0` mempool.space →blockstream.info →	925776	`SENTINEL\|SESSION\|f1c2b10af79f185616bea2ff183d68f…`
RUN013 – AUDITLOGAI_HMAC_TAMPER (Context)	Sentinel.QMS.v4.Amplify.REPRODUCIBILITY.049	`2f5682c4…a81eac` mempool.space →blockstream.info →	925786	`SENTINEL\|SESSION\|16a43d8320fec3f071b542526b6ad43…`
RUN016 – QMS Aggregator (Context)	Sentinel.QMS.v4.Amplify.REPRODUCIBILITY.061	`0915251f…313262` mempool.space →blockstream.info →	925812	`SENTINEL\|SESSION\|c1058654ce59718fa6deaee28cbe216…`

Note: OP_RETURN payloads are hash-only. No evidence or PHI is written on-chain. Interpretation and disposition remain the responsibility of CROs, sponsors, and regulators.