Tweetkeep proof for X post 2111153378009194648 by @RabbiJeffx
https://x.com/RabbiJeffx/status/2111153378009194648
First archived 2026-10-16 17:54 UTC

Post text, saved 2026-10-16 17:54 UTC
  File     https://tweetkeep.com/proof/2111153378009194648/text
  SHA-256  e03104d7b4fa8d2f1552e561b5c7dfcdee22952d75ea35f1ced4e13707fee897
  Listed in https://tweetkeep.com/data/proofs/2026-10-16T1836.txt
  Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-16T1836.txt.ots

Page snapshot, saved 2026-10-16 17:54 UTC
  File     https://tweetkeep.com/data/snaps/2111153378009194648_0.png
  SHA-256  73f3826d5f46cc8253c4005289fbebc628d2b02135160195cc0a6ce3fdc3fda0
  Listed in https://tweetkeep.com/data/proofs/2026-10-16T1836.txt
  Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-16T1836.txt.ots

X's own data for this post, saved by the Internet Archive (Wayback Machine), captured 2026-10-17 02:46 UTC:
  https://web.archive.org/web/20261017024644/https://cdn.syndication.twimg.com/tweet-result?id=2111153378009194648&token=548dtl8qae7&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