Dmitrii Zatona

An engineering analysis of the FBI Threat Screening Center AI RFI: why record-level, tamper-evident provenance exceeds what any lineage tool ships today.

ATL Protocol v2.0 flips the PKI model: verifiers don't need the log operator's public key to validate a receipt. The recommended path roots trust in external anchors (RFC 3161 TSA, Bitcoin OTS); the Ed25519 signature is available as an additional integrit

ATL Protocol uses a two-level Merkle tree architecture where short-lived Data Trees feed into an eternal Super-Tree. A genesis leaf with a domain separator cryptographically chains trees together. Two receipts and one function call prove the entire log wa

Building RFC 9162 consistency proofs for ATL Protocol, I took a shortcut that turned out to be exploitable. The story of a simplified implementation, the attack that broke it, and the full RFC 9162 verification that replaced it -- with five invariants, co

The checkpoint wire format in ATL Protocol: a fixed 98-byte binary blob with no parser, no ambiguity, and a signature that lives outside the signed data. A byte-by-byte walkthrough of the design decisions behind cryptographic checkpoints.