Tweetkeep proof for X post 2110714264805576914 by @RabbiJeffx
https://x.com/RabbiJeffx/status/2110714264805576914
First archived 2026-10-15 12:51 UTC

Post text, saved 2026-10-15 12:51 UTC
  File     https://tweetkeep.com/proof/2110714264805576914/text
  SHA-256  11eac203be0ae3374560ec9a4b3fb85598c4f9323d570486806cef230f0dd15d
  Listed in https://tweetkeep.com/data/proofs/2026-10-15T1314.txt
  Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-15T1314.txt.ots

Page snapshot, saved 2026-10-15 12:51 UTC
  File     https://tweetkeep.com/data/snaps/2110714264805576914_0.png
  SHA-256  2c08279ad5ced5183890dcbfc13024292590028e427f6c969acedd474c7ca36d
  Listed in https://tweetkeep.com/data/proofs/2026-10-15T1314.txt
  Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-15T1314.txt.ots

Page snapshot, saved 2026-10-16 12:47 UTC
  File     https://tweetkeep.com/data/snaps/2110714264805576914_1.png
  SHA-256  f46bf5f2bb0d4684812eaf5f4c520f12a0e76e9c69fe987123a19238e4c88427
  Listed in https://tweetkeep.com/data/proofs/2026-10-16T1336.txt
  Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-16T1336.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