Tweetkeep proof for X post 2111165753009549471 by @RabbiJeffx
https://x.com/RabbiJeffx/status/2111165753009549471
First archived 2026-10-16 18:55 UTC

Post text, saved 2026-10-16 18:55 UTC
  File     https://tweetkeep.com/proof/2111165753009549471/text
  SHA-256  b13df2b8ecd5fe38b7b7cfdf525a8e34ccd0bb2b256911c9ff7afbcd9f8954af
  Listed in https://tweetkeep.com/data/proofs/2026-10-16T1936.txt
  Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-16T1936.txt.ots

Page snapshot, saved 2026-10-16 18:55 UTC
  File     https://tweetkeep.com/data/snaps/2111165753009549471_0.png
  SHA-256  8e90495279261dd6a42d19099a783aa9359c1731b38ac0a4a3e84e1b8cdcf449
  Listed in https://tweetkeep.com/data/proofs/2026-10-16T1936.txt
  Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-16T1936.txt.ots

X's own data for this post, saved by the Internet Archive (Wayback Machine), captured 2026-10-17 02:36 UTC:
  https://web.archive.org/web/20261017023652/https://cdn.syndication.twimg.com/tweet-result?id=2111165753009549471&token=548f7z3iiu&lang=en

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