Loading ForensicBlock
Preparing your blockchain forensics platform...
Preparing your blockchain forensics platform...
Two adjacent document generators we ship for the lanes that need them. Both are templated and deterministic — the lawyer reading the output expects predictable, editable, lawyer-friendly text. Neither uses an LLM in the path. Both are DRAFT-marked on every page; ForensicBlock does not practice law and does not file SARs.
Pre-fills from case_info + caller-supplied recipient + attorney. Subjects table, deposit evidence with tx hashes, records-to-request switches (KYC, transaction history, login records, IP, deposit attribution).
FinCEN-shaped narrative + structured envelope. Activity category allowlist. Subjects with addresses + ID docs. Activity description with cited transaction hashes.
'ForensicBlock does not practice law, does not provide legal advice [or file SARs], and is not party to this matter. Issuing counsel / filing compliance officer is solely responsible for the final document.'
Subpoena builder mounts on litigation / asset-recovery / insolvency lanes. SAR builder mounts on compliance matters.
Forms collect the recipient (subpoena) or filing institution (SAR) + the parties involved + the on-chain evidence.
Subpoena: KYC, transaction history, login records, IP, deposit attribution. SAR: structuring / ML / TF / fraud / identity theft / cyber / other.
Templated body composed with section headers, citation table, DRAFT NOTICE on every page.
Copy to clipboard or .txt download. Counsel reviews, edits jurisdiction-specific language, signs, serves / files.
Honesty rail
Both generators are DETERMINISTIC. Same input → same output. No LLM in the path. The lawyer reading the result gets predictable, editable text they can trust. We never invent legal language; we structure the boilerplate so the lawyer's time goes to substance.
Book a demo and bring a closed matter (or a hypothetical one).