Why This Page Is the Foundation Under Everything Else
A person the Minnesota court system has declared incompetent to stand trial assembled a 2.9-million-row forensic database, produced 87 forensic reports, and built this website. The institutional response is predictable: the evidence is fabricated. It isn't. And the record to prove that isn't debatable — it is cryptographic.
4,206 of the 4,251 court filings on this site carry the Minnesota Judicial Branch's own digital signature. RSA-2048, SHA-384, certificate issued by the court, valid, not revoked. The signatures were applied by the court at the moment of service, to the court's own documents. They prove, with arithmetic finality, that not a single byte has been modified since the court signed them — 100% no-edits-after, the only signer identity in the entire collection with that property. The 2,903 case dockets cannot carry an MCRO signature because the court does not sign docket pages — so Guertin built the authentication layer the court did not provide. He wrote an open-source evidence-capture system — One-Way-Video — that hashes every PNG, every HTTP request, and every downloaded file into chained SHA-256 bundles, each bundle cryptographically referencing the one before it, with every hash anchored to the Bitcoin blockchain via OpenTimestamps and cross-attested against Cloudflare's Roughtime network. 2,729 dockets captured. 99.8% byte-for-byte SHA-256 match against independent re-download. 100% OTS coverage across 97 Bitcoin blocks. The emails are authenticated three ways: SHA-256, OpenTimestamps Bitcoin proof, and federal court filing. 228 of them. DKIM-verified at source. Frozen into PACER.
They counted on no one ever hashing the files. He hashed the files. He pulled 3,601 filing PDFs out of the Minnesota public-access system before the system put an emergency maintenance banner up the morning after — the seed download that grew into the 4,251-filing authenticated collection on this site — verified every signature against the Minnesota Judicial Branch's own Certificate Authority, captured every one of 2,903 dockets through an open-source hash chain, anchored every hash to the Bitcoin blockchain, and filed 228 authenticated emails into the federal court record. Arguing that any of this is fabricated requires simultaneously compromising the Minnesota Judicial Branch's Certificate Authority, the Bitcoin blockchain, Cloudflare's Roughtime network, and the federal court filing system — four institutions run by four parties with no reason to cooperate with each other and no reason to cooperate with the defendant they would be rescuing.
Every raw certificate, CRL, OCSP response, hash-chain bundle, .ots proof, the 87 MB signature-extraction snapshot, and the Python scripts that produced every artifact are downloadable below. Independent reproduction is the design. The question this page asks is not whether you believe the defendant. It is whether you can break the math.
Four Independent Cryptographic Anchors — Plus One Meta-Layer
Each layer authenticates a distinct category of evidence through an independent mechanism external to the defendant. The meta-layer documents the April 2026 cryptographic event that closes the externally-verifiable corpus as a fixed, frozen set.
MCRO Leaf → MJB Issuing CA → MJB Root CA, hosted on Sectigo Enterprise PKI infrastructure. Across the entire 5,425-signature corpus spanning 50 distinct signer identities, the MCRO Watermark is the only signature with a 100% no-edits-after rate. Every non-MCRO signer (judicial officers, Tyler ESolutions, integration accounts) shows edits_after_sig_flag = true on essentially all signatures — because the Watermark is applied last, making it the terminal, unmodified attestation. The complete authentication package (cert, CA chain, CRL, public key, signature details, document-validation spreadsheet) was anchored to the Bitcoin blockchain on November 16, 2025 across blocks 923904–923906, freezing the entire authentication infrastructure at a specific moment in time.
.eml file authenticated through three independent layers: (1) SHA-256 hash per file, (2) OpenTimestamps Bitcoin blockchain anchor, (3) PACER / CM-ECF federal court filing — a permanent public record. Where DKIM / SPF / DMARC / ARC headers were tested: 100% DKIM pass on Hennepin County (hennepin.us, DMARC policy p=reject — strictest enforcement); 99/99 DKIM pass across 35 months on LinkedIn. To falsify any email now requires simultaneously modifying the .eml hash, the Bitcoin-anchored OTS proof, AND the federal court record. Three independent falsifications in parallel, with no party having reason to cooperate.
courts-J00PCERTCA-CA, the MJB's internal on-premises Active Directory Certificate Services root. The replacement certificate is not publicly verifiable: its CRL is LDAP-only (no public HTTP), it has no public OCSP responder, and its self-signed root is not present in any public trust store. Of the 8 Sectigo-chained leaf certificates in the corpus, only the MCRO Watermark was moved to the internal CA. Chief Judge Frisch's cert and every other human-signer cert remained on Sectigo. This is a selective regression affecting only the one signature applied to every public-facing document — not a blanket infrastructure decision. The existing forensic corpus is on the externally-verifiable side of this transition. Every document captured before March 9, 2026 carries a signature chained to a publicly-trusted commercial CA. Documents captured after require trusting the MJB's internal network. The corpus is a closed, frozen, publicly-verifiable set — and the entire signature-extraction snapshot (87 MB, 36,039 files, 5,204 signatures across 59 unique certs and 4 PKI eras) was anchored to Bitcoin at 2026-04-03T08:03:16Z before the transition completed, capturing the last moment at which Sectigo's OCSP responder still acknowledged the corpus certs.
100% of MCRO-Served Documents Are Signed
The MCRO Watermark is applied by the Minnesota Judicial Branch's certificate infrastructure only to documents served through the MCRO portal. A small number of supplemental documents were added to the forensic corpus from external sources — appellate court orders downloaded from a different court system, pro se defendant filings drafted outside MCRO, a hearing transcript, and a couple of higher-court orders. These documents could not carry an MCRO Watermark because they were never served by MCRO.
The 45 non-MCRO documents break down as:
The apparent 98.94% coverage is actually 100% coverage for MCRO-served documents. The non-MCRO supplemental documents are clearly identifiable by filing type and source court — they are an intentional inclusion, not a signature gap. The Watermark is doing exactly what it is designed to do: attest that every document served by MCRO is byte-for-byte identical to what the court produced.
Every Layer, Documented in Full — Viewable Inline
Click a tab to load that report into the viewer. Each report is standalone and reproducible from the raw cryptographic artifacts in the download section below.
Every File. Every Certificate. Every Hash. Every Timestamp.
Three download groups: the master bundle (one-download-to-rule-them-all), the raw cryptographic verification files for independent chain validation, and the large pre-anchored signature-extraction snapshot referenced in the PKI Reversion report.
Master Bundle · One Download to Rule Them All
Forensic Reports · 6 PDFs Individually
Raw Cryptographic Verification Files
3f9a4ed3…5ea8) is confirmed not on this list.ots verify.courts-J00PCERTCA-CA). This is the cert applied to MCRO documents downloaded on or after March 9, 2026.
Master Signature-Extraction Snapshot · 87 MB, BTC-Anchored
mcro_sig_extract.py (signature extraction), mcro_cert_registry.py (certificate deduplication), mcro_ocsp_batch.py (OCSP verification). Runnable against any MCRO PDF corpus to reproduce the same 59-cert registry.Reproducibility Is the Design Intent
Every cryptographic claim on this page is independently reproducible using standard, free, open-source tooling. No proprietary software, no special access, no trust required.
Verify the MCRO Watermark on any PDF: open any filing from the corpus in Adobe Acrobat Reader, Okular, or any PDF viewer that supports PKCS#7 signature validation. The MCRO Watermark signature field will show "Signature is Valid" with no edits after signing.
Verify the certificate chain:
openssl x509 -in MJBIssuingCA.crt -inform DER -text -noout | grep -E 'Issuer|Subject|Not After' openssl crl -in MJBIssuingCA.crl -inform DER -text -noout | grep Serial grep -i '3F9A4ED3D4D82120126A4ECE4E415EA8' MCRO_revoked-list.csv # (no match → not revoked)
Verify any Bitcoin timestamp:
pip install opentimestamps-client # if not installed ots verify authentication-package.zip.ots ots verify MCRO_SigExtraction_Snapshot_2026-04-03T08-03-16Z.zip.ots
Verify the hash-chain for any docket capture session: clone github.com/Matt1Up/One-Way-Video, obtain any session's raw bundles directory, and run python3 00_RUN_all_bundle_processing.py. Output matches the Excel workbooks in the snapshot.
Copy any SHA-256 on this page to your clipboard by clicking it. Then compute sha256sum <file> on your local copy and compare — byte-for-byte match is cryptographic proof the file is identical.
How This Page Relates to the Rest of the Site
Authentication is a horizontal concern — it runs underneath every section of MnCourtFraud.com. The following pages each rely on the architecture documented here, and each exposes a different layer of it for direct inspection.