Preparing your blockchain forensics platform...
Every 24 hours ForensicBlock computes a SHA-256 Merkle root over each org's previous-day audit-log entries and chain-links it to the prior day — a tamper-evident sequence you can cold-verify with no account. Each root is also RFC 3161 timestamped and anchored to Bitcoin via OpenTimestamps. Paste the printed root or attestation id to verify.
All anchors present on this row: Merkle root, RFC 3161 timestamp token, and a confirmed on-chain anchor — each independently checkable.
Merkle root (SHA-256)
669228d13e8ef12e97c1a88c067b103bef5f3f3c6af87e724e8a89795ad686ff
Token hex (first 64 chars of DER)
3082122130030201003082121806092a864886f70d010702a082120930821205
Verify independently with openssl ts -verify against the TSA's CA chain.
Verify independently with ots verify (or upload the .ots at opentimestamps.org) — it checks the Merkle root is committed in Bitcoin block 966304.
Returned by fb_attestation_verify_public v0.2.0.
Verify another attestation
SHA-256 binary Merkle tree over each org's previous calendar day of audit-log entry hashes. The root is the leaf-set's cryptographic fingerprint — cold-verifiable from any browser.
Each daily attestation references the previous day's SHA-256. Altering any past day breaks every subsequent link — a tamper-evident sequence, no third party required.
The root is submitted to a public TSA (FreeTSA / DigiCert / Sectigo). The signed token proves the root existed by that wall-clock moment — back-dating is impossible.
The root is anchored to Bitcoin via OpenTimestamps — no wallet, no gas. Once a Bitcoin block confirms it, the .ots proof is independently checkable with `ots verify` against Bitcoin's chain.