Tweetkeep proof for X post 2112551963099287618 by @xIsraelExposedx
https://x.com/xIsraelExposedx/status/2112551963099287618
First archived 2026-10-20 15:56 UTC

Post text, saved 2026-10-20 15:56 UTC
  File     https://tweetkeep.com/proof/2112551963099287618/text
  SHA-256  3ba5bb6a7f752312c0cf8f89916b84b998aebf922e4a4a21c855b03d484a371c
  Listed in https://tweetkeep.com/data/proofs/2026-10-20T1629.txt
  Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-20T1629.txt.ots

Page snapshot, saved 2026-10-20 16:04 UTC
  File     https://tweetkeep.com/data/snaps/2112551963099287618_0.jpg
  SHA-256  b865b2ee7a7f95fc860c6c174f308cfc84a73c2825c368fd356b4017c0c19ec5
  Listed in https://tweetkeep.com/data/proofs/2026-10-20T1629.txt
  Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-20T1629.txt.ots

X's own data for this post as it reached our browser, as WARC records (open with any WARC tool, e.g. https://replayweb.page):
  2026-10-20 15:56 UTC  https://tweetkeep.com/warc/834.warc.gz
    SHA-256  838e4623cf5c42fc93736f8a77078c2cfab0a388f4aedfeeb677f2f08e90ce0d
    Listed in https://tweetkeep.com/data/proofs/2026-10-20T1629.txt

No Internet Archive copy: we ask it for a few hundred fresh posts a day, from the accounts that delete the most. X's data for every post is in the WARC records above.

How to check:
1. Download a file above and run: shasum -a 256 <file>. It must print the SHA-256 shown, and that hash must appear in the list.
2. Drop the list and its .ots file on https://opentimestamps.org, or run: ots verify <list>.ots
   That proves the list, and every file whose hash it holds, existed unchanged by then. Fresh timestamps reach Bitcoin within hours.
More: https://tweetkeep.com/faq#proof