Tweetkeep proof for X post 2110134388948361351 by @RabbiJeffx https://x.com/RabbiJeffx/status/2110134388948361351 First archived 2026-10-13 22:26 UTC Post text, saved 2026-10-13 22:26 UTC File https://tweetkeep.com/proof/2110134388948361351/text SHA-256 3869aadec0530f30359c686c72e972ce3bafdf2c09832df532a50db7d1fc064f Listed in https://tweetkeep.com/data/proofs/2026-10-13T2325.txt Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-13T2325.txt.ots Page snapshot, saved 2026-10-13 22:26 UTC File https://tweetkeep.com/data/snaps/2110134388948361351_0.png SHA-256 0c74dd367914de6b97e1dc9dd0196ae48a948de45dff2fa5eb9d8553b09b0842 Listed in https://tweetkeep.com/data/proofs/2026-10-13T2325.txt Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-13T2325.txt.ots X's own data for this post, saved by the Internet Archive (Wayback Machine), captured 2026-10-14 01:01 UTC: https://web.archive.org/web/20261014010100/https://cdn.syndication.twimg.com/tweet-result?id=2110134388948361351&token=5456krsg6tq&lang=en How to check: 1. Download a file above and run: shasum -a 256 . 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 .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