@whoisjmichaelon X · 2026-10-02
A tamper-evident, on-chain timestamp of what this post said. Captured 2026-10-02 19:27 UTC.
Flock Safety sent me a cease-and-desist letter threatening litigation over the cybersecurity research I published on https://t.co/QsaSFsUOBN. A journalist has since shared the email Flock sent its customers, which calls me a malicious actor, says the company has notified law enforcement, and pledges to take my research offline. That email confirmed my thesis. Flock admits that when it closed the issue in December, it found no indication of unauthorized access to its data, and by its own account it only learned of what it now alleges after I published. My thesis is that a company holding the movements of nearly every American, yet unable to detect its own data leaving, is a national security threat, because a foreign adversary will never publish a paper to tip them off. I'm not backing down, so read the documents for yourself and stand with me at https://t.co/aj7KhEVGyt
Linked media above is notarized by reference — bsv.cx captured the link's title and preview image at archive time; it does not host the linked video or page.
Verify it yourself: the manifest is the exact JSON whose
SHA-256 is 8d065aa90481b9a8cc60c91ecb48de289805d71c9b676d049c8aa89ba4fcf9ab; it binds the tweet id, author, post time, and the SHA-256 of the text above. Re-hash the text to match 9fd86bb5e0fabbbd403d411c64716f46e8e8a3649a832462d30ccc50bbbab8a7, and read the anchor transaction's OP_RETURN
bsv.cx / x1 / 8d065aa90481b9a8cc60c91ecb48de289805d71c9b676d049c8aa89ba4fcf9ab — the block's timestamp proves the post said this at or before that time,
with no trust in bsv.cx. Content archived via the X API.