Tweetkeep proof for X post 2111287582931984433 by @MarioNawfal https://x.com/MarioNawfal/status/2111287582931984433 First archived 2026-10-17 02:53 UTC Post text, saved 2026-10-17 02:53 UTC File https://tweetkeep.com/proof/2111287582931984433/text SHA-256 559ff8fd957105242b28448f33e337c21f91f80421c518b5305cd995d7a59ea1 Listed in https://tweetkeep.com/data/proofs/2026-10-17T0336.txt Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-17T0336.txt.ots Page snapshot, saved 2026-10-17 02:54 UTC File https://tweetkeep.com/data/snaps/2111287582931984433_0.png SHA-256 5089b2410fbe68d79dd49e8f7d6cb6cad965839dcfd4f001c72954f0327ef851 Listed in https://tweetkeep.com/data/proofs/2026-10-17T0336.txt Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-17T0336.txt.ots X's own data for this post, saved by the Internet Archive (Wayback Machine), captured 2026-10-17 02:56 UTC: https://web.archive.org/web/20261017025600/https://cdn.syndication.twimg.com/tweet-result?id=2111287582931984433&token=548t7q2ub&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