Tweetkeep proof for X post 2111581771598905816 by @MarioNawfal https://x.com/MarioNawfal/status/2111581771598905816 First archived 2026-10-17 22:22 UTC Post text, saved 2026-10-17 22:22 UTC File https://tweetkeep.com/proof/2111581771598905816/text SHA-256 ac49dd0360ef7cd31e680fcf860da8022776e78c3f9e65effeaf90225d2d124f 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 22:23 UTC File https://tweetkeep.com/data/snaps/2111581771598905816_0.png SHA-256 cb5a26c4e5a4f3a80e892417cd4aea7291b9a0a79a3d58c25f010583c936597e 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:24 UTC: https://web.archive.org/web/20261018012425/https://cdn.syndication.twimg.com/tweet-result?id=2111581771598905816&token=549q9sozqy&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