@charliekirk11on X · 2023-12-01
A tamper-evident, on-chain timestamp of what this post said. Captured 2026-09-11 00:29 UTC.
I was smeared as an anti-Semite and “Holocaust denier” for even broaching this topic. Turns out I was onto something….. “Israeli officials obtained Hamas’s battle plan for the Oct. 7 terrorist attack more than a year before it happened, documents, emails and interviews show. But Israeli military and intelligence officials dismissed the plan as aspirational, considering it too difficult for Hamas to carry out. The approximately 40-page document, which the Israeli authorities code-named “Jericho Wall,” outlined, point by point, exactly the kind of devastating invasion that led to the deaths of about 1,200 people. The translated document, which was reviewed by The New York Times, did not set a date for the attack, but described a methodical assault designed to overwhelm the fortifications around the Gaza Strip, take over Israeli cities and storm key military bases, including a division headquarters. Hamas followed the blueprint with shocking precision.” https://t.co/mL6H1v5jk0
Verify it yourself: the manifest is the exact JSON whose
SHA-256 is a6bea27a918549af21cc46d2df41f0767177a97a390405b0789af775ce02355e; it binds the tweet id, author, post time, and the SHA-256 of the text above. Re-hash the text to match ca1e8541aada2e21959518f7f196914caf80ad07d20d1c8cf20af76886ac7901, and read the anchor transaction's OP_RETURN
bsv.cx / x1 / a6bea27a918549af21cc46d2df41f0767177a97a390405b0789af775ce02355e — 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.