Tweetkeep proof for X post 2110416384358252710 by @MarioNawfal https://x.com/MarioNawfal/status/2110416384358252710 First archived 2026-10-14 17:13 UTC Post text, saved 2026-10-14 17:13 UTC File https://tweetkeep.com/proof/2110416384358252710/text SHA-256 37d140c02733f085330780f4263275c94012f9e18b10555ceced17975dc101a5 Listed in https://tweetkeep.com/data/proofs/2026-10-14T1741.txt Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-14T1741.txt.ots Page snapshot, saved 2026-10-14 17:13 UTC File https://tweetkeep.com/data/snaps/2110416384358252710_0.png SHA-256 cc5f4c614dcf8a770ed7d414aeb65e274df3890b33367603b7fdb7d5eb2137ea Listed in https://tweetkeep.com/data/proofs/2026-10-14T1741.txt Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-14T1741.txt.ots X's own data for this post, saved by the Internet Archive (Wayback Machine), captured 2026-10-15 03:35 UTC: https://web.archive.org/web/20261015033500/https://cdn.syndication.twimg.com/tweet-result?id=2110416384358252710&token=5462gxyuja&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