Tweetkeep proof for X post 2111593857154429270 by @MarioNawfal https://x.com/MarioNawfal/status/2111593857154429270 First archived 2026-10-17 23:08 UTC Post text, saved 2026-10-17 23:08 UTC File https://tweetkeep.com/proof/2111593857154429270/text SHA-256 d25903db50e934dd00a2795cffd2002cafd8a08b00e540a83e7cbc88c39bc999 Listed in https://tweetkeep.com/data/proofs/2026-10-17T2319.txt Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-17T2319.txt.ots Page snapshot, saved 2026-10-17 23:08 UTC File https://tweetkeep.com/data/snaps/2111593857154429270_0.png SHA-256 6216744e5f247c60c6131865ba4e2379ecf8c0b86763e5d6a7d19a375dbf3fdf Listed in https://tweetkeep.com/data/proofs/2026-10-17T2319.txt Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-17T2319.txt.ots X's own data for this post, saved by the Internet Archive (Wayback Machine), captured 2026-10-18 01:01 UTC: https://web.archive.org/web/20261018010103/https://cdn.syndication.twimg.com/tweet-result?id=2111593857154429270&token=549rn3i9d&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