What Just Happened?

Someone asked: did your AI take action X during time period T?

This receipt is the cryptographic proof that the answer is no — and that the no is structurally guaranteed, not just an absence of records.

Negative-case proof is the hardest evidentiary primitive in existing AI compliance. Logs cannot prove a non-occurrence. Receipts can.

How It Worked, In Three Steps

Step 1
Question Posed
A specific action and time window were specified for verification — for example, 'did the trading AI execute any trades during the regulatory blackout window of 14:00-14:30 UTC?'
Step 2
State Examined
System logs, constraint state, and execution records were deterministically examined for the entire time window.
Step 3
Non-Occurrence Proven
Cryptographic proof of non-occurrence issued, with attestation that the system was operational and recording during the entire period.

What This Receipt Proves

Why This Matters Legally

This proof complies with the following regulations and statutes:

GDPR · Article 17
Regulation (EU) 2016/679 — Right to Erasure
"The data subject shall have the right to obtain from the controller the erasure of personal data concerning him or her."
→ Read on gdpr-info.eu
SEC Rule 10b-5
17 CFR § 240.10b-5 — Trading Restrictions
"It shall be unlawful for any person… to engage in any act, practice, or course of business which operates or would operate as a fraud or deceit upon any person."
→ Read on Cornell Law

Verify This Receipt Yourself

You don't have to trust us. You can check this proof, end-to-end, in one click.

VERIFY NOW

When you click Verify, your browser will:

  1. Re-compute the receipt's cryptographic fingerprints
  2. Confirm those fingerprints match what's stored on Bitcoin
  3. Verify the signature was produced by an authorized signer
  4. Show you a plain "VERIFIED" or "INVALID" result

No cryptography knowledge required. No Genesis Protocol cooperation required. The proof stands on its own.

For Technical Reviewers — click to expand

Cryptographic Fingerprints

SHA-256c4b7d3f6a1e5c8d2b9f4e7a3c6d1b8f5e2a9c4d7b3e6f1a8c5d2b9e4f7a8f3e9
SHA3-256d6b4f1e7c5a9d2b8f3e6c1a4d7b2f5e8a3c6d9b4f1e7a2c5d8b3f6b9c3f5e8a2
BLAKE3b3:e6b9c2f5a8d1b4e7c3f6a9d2b5e8c1f4a7d3b6e9c2f5a8d1b4e7c3c1d4f7a3

Bitcoin Anchor

Calendar Quorum4 of 4
Block Height875,234
Block Hash00000000000000000003a7b8c5f1d4e9b2a6c8f3d7e1b5a9c4f6d2b8e3a7c1f5
Anchor Time UTC2026-04-30T18:42:11Z

Signature

AlgorithmML-DSA-87 (FIPS 204)
Verifier Instancegvef-prod-001
Pubkey Fingerprintsha256:e7c3f6a9d2b5e8c1f4a7d3b6e9c2f5a8d1b4e7c3f6a9d2b5e8c1f4a7d3b6e9c2

Constitutional Anchor

CS₀b8263fe7d942f304c05751f5b8c6dccb7bc352280ca0114ea5c66b5174ee393c
GENESIS-BLOCKb1c57f72
ANCHORfa39bbe8

GPOC Chain Commitment

Sequence3
Sequence Rootb3:cbb2203cdfd8cccfd1b8e2209219c83c2b0c08b614ba43430dc177d62255320f

Issued By

EntityPoint Break Trading Group LLC
EIN41-5327323
FounderChristian John McGowan
Co-founderLiam McGowan
Contactpointbreaktradingedu@gmail.com
Websitegenesisprotocol.ai