Loading ForensicBlock
Preparing your blockchain forensics platform...
Preparing your blockchain forensics platform...
Pillar 2 of the doctrine: when a firm has FINCEN / OFAC / court-ordered compliance obligations, the artifact they produce should be self-authenticating. Sealed Screening Records do that — each record is a snapshot of a watchlist screening run with a SHA-256 self-hash and a public verifier URL. Anyone can confirm the seal.
5 trigger types: scheduled / manual / on_disbursement / on_intake / on_close. The firm's compliance policy maps onto these.
Canonical content hashed; sealed_at + sealed_by + sealed_content_sha256 stamped. SQL trigger refuses post-seal mutation of the core.
Anyone (opposing counsel, regulator, journalist) drops the ID or hash at /verify-screening-record and sees the seal confirmation. No login. Browser-only.
On /organizations/[id]/screening-records, click Produce sealed record.
Scheduled / manual / on_disbursement / on_intake / on_close. Records the why-now.
Active entries snapshotted. Per-entry lines written. SHA-256 of canonical form stamped.
Verifier URL is on the record. Public; no account; works in any browser.
Returns: record exists, sealed, methodology version, entries screened, hit counts. Never the line-level entries (those stay confidential).
Honesty rail
The verifier never exposes the lines (the actual addresses screened). That's confidential matter content. The issuing firm provides line-level detail under your discovery / regulatory request.
Book a demo and bring a closed matter (or a hypothetical one).