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

Post text, saved 2026-10-15 10:34 UTC
  File     https://tweetkeep.com/proof/2110679688435683583/text
  SHA-256  2aa1e056fbc93a882504941ff16c1273265ab375dcd69956fe2711edc4a3aad5
  Listed in https://tweetkeep.com/data/proofs/2026-10-15T1114.txt
  Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-15T1114.txt.ots

Page snapshot, saved 2026-10-15 10:34 UTC
  File     https://tweetkeep.com/data/snaps/2110679688435683583_0.png
  SHA-256  7d12b53f138a741fb51c18296157aa00611ca6b281307148ffba007c588bb920
  Listed in https://tweetkeep.com/data/proofs/2026-10-15T1114.txt
  Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-15T1114.txt.ots

Page snapshot, saved 2026-10-16 10:30 UTC
  File     https://tweetkeep.com/data/snaps/2110679688435683583_1.png
  SHA-256  318e62ebfc0d3b220568529d61fede0a7333a9525deaddc70b8cd85631a22c4e
  Listed in https://tweetkeep.com/data/proofs/2026-10-16T1036.txt
  Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-16T1036.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