Tweetkeep proof for X post 2111550803756351549 by @RabbiJeffx
https://x.com/RabbiJeffx/status/2111550803756351549
First archived 2026-10-17 20:12 UTC

Post text, saved 2026-10-17 20:12 UTC
  File     https://tweetkeep.com/proof/2111550803756351549/text
  SHA-256  433ef7c2ed57ba2cc7e1fbe0fd1e81b8ef3cbe8becf448a66548fda6555b4b98
  Listed in https://tweetkeep.com/data/proofs/2026-10-17T2019.txt
  Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-17T2019.txt.ots

Page snapshot, saved 2026-10-17 20:12 UTC
  File     https://tweetkeep.com/data/snaps/2111550803756351549_0.png
  SHA-256  b8fa305eab73f3b4de4a87b0d174a4cbbab90508af4359607229a93e282d489a
  Listed in https://tweetkeep.com/data/proofs/2026-10-17T2019.txt
  Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-17T2019.txt.ots

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