Tweetkeep proof for X post 2110662670772789288 by @RabbiJeffx
https://x.com/RabbiJeffx/status/2110662670772789288
First archived 2026-10-15 09:33 UTC

Post text, saved 2026-10-15 09:33 UTC
  File     https://tweetkeep.com/proof/2110662670772789288/text
  SHA-256  f4718747e52b489f505fea588955cb2a1c170b08046d45d9f8f925633682768c
  Listed in https://tweetkeep.com/data/proofs/2026-10-15T1014.txt
  Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-15T1014.txt.ots

Page snapshot, saved 2026-10-15 09:34 UTC
  File     https://tweetkeep.com/data/snaps/2110662670772789288_0.png
  SHA-256  3afdbec82a696a44c39dc3ce73995da07b8a5700fc53e1c798050c23161b96fb
  Listed in https://tweetkeep.com/data/proofs/2026-10-15T1014.txt
  Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-15T1014.txt.ots

Page snapshot, saved 2026-10-16 09:22 UTC
  File     https://tweetkeep.com/data/snaps/2110662670772789288_1.png
  SHA-256  140fac9bb758c89620d08acd82adfc7b99416ba2bc37ef4da2f0795279bd2bde
  Listed in https://tweetkeep.com/data/proofs/2026-10-16T0936.txt
  Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-16T0936.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