Tweetkeep proof for X post 2111056133905355175 by @RabbiJeffx
https://x.com/RabbiJeffx/status/2111056133905355175
First archived 2026-10-16 11:35 UTC

Post text, saved 2026-10-16 11:35 UTC
  File     https://tweetkeep.com/proof/2111056133905355175/text
  SHA-256  54f83969e7986e3a49f17cf0f1aa5ac6a14225228a0bd21c4ec459ece370f289
  Listed in https://tweetkeep.com/data/proofs/2026-10-16T1136.txt
  Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-16T1136.txt.ots

Page snapshot, saved 2026-10-16 11:36 UTC
  File     https://tweetkeep.com/data/snaps/2111056133905355175_0.png
  SHA-256  1bfa1291c7f7eeda4caefc47e913d833f131ce450c8013eda741041a91474d12
  Listed in https://tweetkeep.com/data/proofs/2026-10-16T1236.txt
  Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-16T1236.txt.ots

Page snapshot, saved 2026-10-17 11:26 UTC
  File     https://tweetkeep.com/data/snaps/2111056133905355175_1.png
  SHA-256  96f10c2d561e368d9f009ca6fc61271e6206a8044dfd06bca3a15c2721bc4a4f
  Listed in https://tweetkeep.com/data/proofs/2026-10-17T1136.txt
  Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-17T1136.txt.ots

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