Tweetkeep proof for X post 2110909843737309338 by @MarioNawfal https://x.com/MarioNawfal/status/2110909843737309338 First archived 2026-10-16 01:51 UTC Post text, saved 2026-10-16 01:51 UTC File https://tweetkeep.com/proof/2110909843737309338/text SHA-256 79001ece522ad9511a8e7027fb7d427ad3e95919a683ba41bd1791f832b265a6 Listed in https://tweetkeep.com/data/proofs/2026-10-16T0214.txt Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-16T0214.txt.ots Page snapshot, saved 2026-10-16 01:51 UTC File https://tweetkeep.com/data/snaps/2110909843737309338_0.png SHA-256 662f81842c854fc9bc5a2f153ee921f597e1446ef004fe70db0b312f225c4ca3 Listed in https://tweetkeep.com/data/proofs/2026-10-16T0214.txt Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-16T0214.txt.ots X's own data for this post, saved by the Internet Archive (Wayback Machine), captured 2026-10-16 01:52 UTC: https://web.archive.org/web/20261016015249/https://cdn.syndication.twimg.com/tweet-result?id=2110909843737309338&token=547ma1ex16w&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