Sentinel QMS v4 · Bitcoin Anchors · OP_RETURN
Bitcoin Anchors for Sentinel QMS v4 Reproducibility
Every key Stage I–IIIB QMS run is anchored to Bitcoin mainnet using the SENTINEL v4 OP_RETURN schema. This page exposes representative TXIDs, block heights, and payloads so CROs and regulators can independently verify that the sessions described in Ordinal 14 have not changed.
All anchors below reference public Bitcoin transactions; no evidence or PHI is ever embedded on-chain. Only cryptographic digests are published, keeping AuditLog.AI strictly zero-custody.
How to verify an anchor
- Identify the TXID and payload from the table below.
- Open a public Bitcoin explorer (e.g. mempool.space).
- Paste the TXID and confirm the OP_RETURN output matches the SENTINEL payload.
- On your side, recompute the SHA-256 and RIPEMD-160 digests of the frozen session log and confirm they match the OP_RETURN fields.
For full reproducibility context, see the Reproducibility and Technology pages.
Stage I — Amplify Stress Test
| Run / Label | Meta ID | TXID | Block | Payload |
|---|---|---|---|---|
| RUN001 – Amplify Stress Test | Sentinel.QMS.v4.Amplify.REPRODUCIBILITY.001 | 3e9a4db0…4792c4 | 923818 | SENTINEL|SESSION|ddbdb990cd4b0dc8143957418… |
| RUN002 – Amplify Stress Test | Sentinel.QMS.v4.Amplify.REPRODUCIBILITY.005 | 9c2eb239…05d156 | 923939 | SENTINEL|SESSION|99d34e624d3c105aec61a35df… |
Full payloads and additional session anchors are available in the AMPLIFY ledger and Ordinal 14 inscription.
Stage II — Deterministic Re-Audit
| Run / Label | Meta ID | TXID | Block | Payload |
|---|---|---|---|---|
| RUN003 – Deterministic Re-Audit | Sentinel.QMS.v4.Amplify.REPRODUCIBILITY.009 | 9721d684…6af8f7 | 924058 | SENTINEL|SESSION|be31ff46db2b5ddc4fdbe2f29… |
| RUN004 – Deterministic Re-Audit | Sentinel.QMS.v4.Amplify.REPRODUCIBILITY.013 | 4873e651…793e9e | 924061 | SENTINEL|SESSION|98404a94fb61ef21f1277f499… |
Full payloads and additional session anchors are available in the AMPLIFY ledger and Ordinal 14 inscription.
Stage IIIA — Adversarial Tamper Challenge
| Run / Label | Meta ID | TXID | Block | Payload |
|---|---|---|---|---|
| RUN005 – Tamper Challenge Plan | Sentinel.QMS.v4.Amplify.REPRODUCIBILITY.017 | d1d78c40…007682 | 924781 | SENTINEL|SESSION|47c4d5159a6a62eb80096c8b7… |
| RUN009 – Tamper Challenge Result | Sentinel.QMS.v4.Amplify.REPRODUCIBILITY.033 | 9de8e1d1…111d73 | 924793 | SENTINEL|SESSION|0521313f7fc323d51fb68f213… |
Full payloads and additional session anchors are available in the AMPLIFY ledger and Ordinal 14 inscription.
Stage IIIB — Dual-Arm Blind HMAC Challenge
| Run / Label | Meta ID | TXID | Block | Payload |
|---|---|---|---|---|
| Multi-Entity Baseline Corpus | Sentinel.QMS.v4.MultiEntityAnchor.001 | 6e3f0744…1c3e7f | 925073 | SENTINEL|SESSION|158fdb62a83f78bd48017266b… |
| RUN010 – MULTI_BASELINE | Sentinel.QMS.v4.Amplify.REPRODUCIBILITY.037 | 5b0fdf19…54dce0 | 925776 | SENTINEL|SESSION|f1c2b10af79f185616bea2ff1… |
| RUN013 – AUDITLOGAI_HMAC_TAMPER | Sentinel.QMS.v4.Amplify.REPRODUCIBILITY.049 | 2f5682c4…a81eac | 925786 | SENTINEL|SESSION|16a43d8320fec3f071b542526… |
| RUN016 – QMS Aggregator (ALL RUNS) | Sentinel.QMS.v4.Amplify.REPRODUCIBILITY.061 | 0915251f…313262 | 925812 | SENTINEL|SESSION|c1058654ce59718fa6deaee28… |
Full payloads and additional session anchors are available in the AMPLIFY ledger and Ordinal 14 inscription.
Ordinals 11–14 — Public Reproducibility Ledger
| Run / Label | Meta ID | TXID | Block | Payload |
|---|---|---|---|---|
| Ordinal 11 – Human-Executed Reproducibility Audit (RUN015) | ORDINAL11 | a09523a5…7a1540 | 921107 | ORDINAL11|b0c8b2223eab705cac6bf7801b64945f… |
| Ordinal 12 – Sentinel QMS v4 Hash & Anchor Schema | ORDINAL12 | e3dd84f7…fae326 | 921121 | ORDINAL12|fb1822a8113a1b691a7ef64bb7cd64ea… |
| Ordinal 13 – Human-Executed Reproducibility (RUN015) | ORDINAL13 | 66cd04d7…1fb991 | 923689 | ORDINAL13|dd498abe7b95b3faade9b244401a4f68… |
| Ordinal 14 – QMS v4 Machine-Audit Reproducibility | ORDINAL14 | fbecdbc1…8faed2 | 926099 | ORDINAL14|35fc5a55cba8a76c10e19ec281554bc4… |
Full payloads and additional session anchors are available in the AMPLIFY ledger and Ordinal 14 inscription.
Note: all OP_RETURN payloads are hash-only; no evidence or PHI is written to chain.