Tweetkeep proof for X post 2110392009206956210 by @RabbiJeffx https://x.com/RabbiJeffx/status/2110392009206956210 First archived 2026-10-14 15:37 UTC Post text, saved 2026-10-14 15:37 UTC File https://tweetkeep.com/proof/2110392009206956210/text SHA-256 d85c471b53543a5c879451d5c6387498002bed84144c98e808ec6fd4e6f8dbae Listed in https://tweetkeep.com/data/proofs/2026-10-14T1541.txt Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-14T1541.txt.ots Page snapshot, saved 2026-10-14 15:37 UTC File https://tweetkeep.com/data/snaps/2110392009206956210_0.png SHA-256 986d1ef0b5e431ec61d48b944fa08f3d6d3f71364f37c24d499344b89bbb445d Listed in https://tweetkeep.com/data/proofs/2026-10-14T1541.txt Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-14T1541.txt.ots Page snapshot, saved 2026-10-15 15:27 UTC File https://tweetkeep.com/data/snaps/2110392009206956210_1.png SHA-256 a06d3da50c41d9a110fbf8c47ff66190d7c887a0ddf0b9a668fddcf7c670aa80 Not timestamped yet: it goes into the next hourly list X's own data for this post, saved by the Internet Archive (Wayback Machine), captured 2026-10-15 03:52 UTC: https://web.archive.org/web/20261015035207/https://cdn.syndication.twimg.com/tweet-result?id=2110392009206956210&token=545zpo9ct4h&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