Tweetkeep proof for X post 2112204125501100476 by @RabbiJeffx
https://x.com/RabbiJeffx/status/2112204125501100476
First archived 2026-10-19 15:39 UTC, deleted from X 2026-10-19 17:28 UTC

Post text, saved 2026-10-19 15:39 UTC
  File     https://tweetkeep.com/proof/2112204125501100476/text
  SHA-256  5dcdbed8eb5768b57706c1824485a02a5094056981788be41eeb91a9f919e2ad
  Listed in https://tweetkeep.com/data/proofs/2026-10-19T1555.txt
  Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-19T1555.txt.ots

Page snapshot, saved 2026-10-19 15:40 UTC
  File     https://tweetkeep.com/data/snaps/2112204125501100476_0.png
  SHA-256  b14e9e9a994df39631f69361b373ab0458e1811f7dcbf69d8fb9cd50c4892b54
  Listed in https://tweetkeep.com/data/proofs/2026-10-19T1555.txt
  Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-19T1555.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-19 15:55 UTC  https://tweetkeep.com/warc/16.warc.gz
    SHA-256  1a19524c48baedb701215d5594c89680a7743a7901498198f0eff16fb941b124
    Listed in https://tweetkeep.com/data/proofs/2026-10-19T1555.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