Tweetkeep proof for X post 2113383757440770314 by @RabbiJeffx
https://x.com/RabbiJeffx/status/2113383757440770314
First archived 2026-10-22 21:36 UTC

Post text, saved 2026-10-22 21:36 UTC
  File     https://tweetkeep.com/proof/2113383757440770314/text
  SHA-256  eaf3401976cab35bd4b26b9be909666a11214b0117abc23bb2542bd2c2fac281
  Listed in https://tweetkeep.com/data/proofs/2026-10-22T2150.txt
  Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-22T2150.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-22 21:36 UTC  https://tweetkeep.com/warc/3626.warc.gz
    SHA-256  7beb60868b21f9f39a2182918750041d57751ca6a7b592c8e847bce6fce81176
    Listed in https://tweetkeep.com/data/proofs/2026-10-22T2150.txt
  2026-10-22 21:36 UTC  https://tweetkeep.com/warc/3627.warc.gz
    SHA-256  56c5f80704b42c0a7817abf90d00bdd78802b57b7cd7f9598a637b65e0d32340
    Listed in https://tweetkeep.com/data/proofs/2026-10-22T2150.txt

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