Now They Know You Know They Know

Cryptographic receipt, not a complaint.

The fraud is documented across 33 forensic packets totaling hundreds of exhibits, a 2.9-million-row Postgres database built from the actual court PDFs, and a federal record sitting in front of three judges and an Eighth Circuit panel. None of which the Minnesota state-court machinery has acknowledged — by design.

So on the evening of 2026-05-13, the entire corpus was filed at the wire to six separate oversight channels — three federal, three Minnesota state — that each individually claim a mandate over precisely this kind of evidence. Filed live, on screen, every byte captured. Filed not because anyone is expected to act on it — but because once the receipts are cryptographically locked, they cannot be retroactively un-received.

The point of this page is the loop itself. The agencies now have the evidence. The receipt is on the Bitcoin blockchain. What they do with it is their problem.

The master packet (00) is what was attached to every submission. Read it. Read 33.

Six POSTs, six destinations, one 36-minute window.

Toggle the FORM SUBMIT VIEWER in DELIVERED to read the full parsed POST body of each submission as the recording reaches its capture moment — including the verbatim statement that landed in each intake queue.

What came back — confirmation PDFs captured live and sealed.

Hash-chain + dual independent timestamps.

The capture pipeline is OneWayVideo — a controller that runs Firefox routed through mitmproxy, records frames via the OBS virtual camera, and writes a numbered JSON "bundle" every ~7 seconds. Each bundle carries:

Everything that was submitted, plus the back-end that proves it.

Each of the buttons below opens an in-page viewer with the actual PDFs. The first three hold infrastructure exhibits — the full Postgres database export, its source files, the authentication chain, and the project-pipeline documentation. PACKETS & FILES contains the 35 "stuffed" packets with their entire zipped evidence folders embedded directly inside each PDF. PACKETS is the same 35 as a lightweight read-only set.

One stream is contaminated. It doesn't change anything.

The session's streams.http_events field contains data captured by a mitmproxy log ~8 hours before the recording began — a source-file misconfiguration in the bundle writer pulled from the wrong file. The contaminated content is hash-locked into the bundle chain, so it remains cryptographically authentic — it just isn't from this session.

It doesn't matter. Seven other independent provenance layers (live streams.net, live streams.http, OBS PNG hash chain, bundle SHA-256 hash chain, on-screen hash overlay, OpenTimestamps Bitcoin anchoring, and the Roughtime ensemble) all line up perfectly to the same recording timeline. Any tampering with the recording itself would break all of them at once. The http_events miss is acknowledged precisely because the redundancy makes it acknowledgeable — the rest of the record holds independently.

The Attorney General's office sealed it for us.

Roughly 30 seconds after the JotForm POST to mnago.jotform.com landed at 10:35 in the recording, the Office of the Minnesota Attorney General's auto-reply landed in the inbox at 2026-05-13 23:52:33 EDT (= 03:52:33 UTC) — inside the same 36-minute capture window, with submission ID 6545399494205897880 embedded in the subject line.

The reply passed DKIM (2048-bit RSA-SHA256, key selector2.ag.state.mn.us), SPF (smtp.mailfrom=ag.state.mn.us), DMARC (p=none), and ARC on the Microsoft outbound route. The full source — every header, every signature blob, every Authentication-Results line — is preserved below for direct inspection:

That email is the State of Minnesota's own cryptographic signature on a piece of paper that says we received this. It is in our possession. It will not be going anywhere. The same loop closes individually with each of the other five destinations via their respective confirmation pages, all captured and hash-locked.

The reply itself is a textbook artifact of bureaucratic administrative Newspeak — "thank you for your submission... while this Office can not respond to every complaint... appropriate staff." No commitment. No timeline. No acknowledgement of the actual content. The form letter does precisely what form letters do. The cryptographic signature on it, however, is real — and that is what we needed.