Tweetkeep proof for X post 2110762370041553065 by @RabbiJeffx
https://x.com/RabbiJeffx/status/2110762370041553065
First archived 2026-10-15 16:08 UTC

Post text, saved 2026-10-15 16:08 UTC
  File     https://tweetkeep.com/proof/2110762370041553065/text
  SHA-256  b0e846c1996f6b9e97d35c67ec9476149c89dd2a7474c73639cf80ad8ec7d1ed
  Listed in https://tweetkeep.com/data/proofs/2026-10-15T1614.txt
  Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-15T1614.txt.ots

Page snapshot, saved 2026-10-15 16:08 UTC
  File     https://tweetkeep.com/data/snaps/2110762370041553065_0.png
  SHA-256  b505b47d39659ad49ab8f84f57de21ad8b3de5caece035fdd787cc8700963930
  Listed in https://tweetkeep.com/data/proofs/2026-10-15T1614.txt
  Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-15T1614.txt.ots

Page snapshot, saved 2026-10-16 15:59 UTC
  File     https://tweetkeep.com/data/snaps/2110762370041553065_1.png
  SHA-256  c153783e65f7b7a974a7375f80ca381c0ea4522fa15c18eb0d67dc467a765b65
  Listed in https://tweetkeep.com/data/proofs/2026-10-16T1636.txt
  Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-16T1636.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