Hand a hash to the court.
It either matches, or it doesn't.
Public, no account required. Paste a ForensicBlock report number, evidence ID, or SHA-256 hash and we'll check it against the platform's append-only audit chain.
The hash matches, or it doesn't. No middle ground.
1. Hash at sealing
At generation time, every report's canonical bytes get a SHA-256 stamp. That hash is written to the platform's append-only audit chain.
2. Tamper-evident, and immutable at the database
Any change to the report — one character, one comma — changes the SHA-256. Verification surfaces a mismatch instantly.
A sealed, attested exhibit also cannot be deleted or rewritten — not by a user, not by an administrator, and not by the platform's own highest-privilege database credential. That rule is enforced inside the database, not in application code, so there is no console, script or migration that quietly steps around it.
3. Court-ready packet
Court-ready reports carry a Certificate of Authenticity prepared to support self-authentication under FRE 902(13)/(14). Admissibility is the court's determination, in every case.