Tweetkeep proof for X post 2110776222930354274 by @RabbiJeffx https://x.com/RabbiJeffx/status/2110776222930354274 First archived 2026-10-15 17:09 UTC Post text, saved 2026-10-15 17:09 UTC File https://tweetkeep.com/proof/2110776222930354274/text SHA-256 422a02754bb0c9ba2f37cea0a97465f508005a9edd503ad21c5152112a7a3e93 Listed in https://tweetkeep.com/data/proofs/2026-10-15T1714.txt Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-15T1714.txt.ots Page snapshot, saved 2026-10-15 17:09 UTC File https://tweetkeep.com/data/snaps/2110776222930354274_0.png SHA-256 1aa44a55a6081705f4b0ff6e515d977b44d9ac03932a6580c0e6e535e649e757 Listed in https://tweetkeep.com/data/proofs/2026-10-15T1714.txt Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-15T1714.txt.ots X's own data for this post, saved by the Internet Archive (Wayback Machine), captured 2026-10-16 02:37 UTC: https://web.archive.org/web/20261016023748/https://cdn.syndication.twimg.com/tweet-result?id=2110776222930354274&token=5477623xwk&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