Tweetkeep proof for X post 2111601904115761286 by @MarioNawfal https://x.com/MarioNawfal/status/2111601904115761286 First archived 2026-10-17 23:38 UTC Post text, saved 2026-10-17 23:38 UTC File https://tweetkeep.com/proof/2111601904115761286/text SHA-256 728346531bd78855962b0dd58ea334f25a453c56180bd88fd656698a729aad0a Listed in https://tweetkeep.com/data/proofs/2026-10-18T0019.txt Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-18T0019.txt.ots Page snapshot, saved 2026-10-17 23:39 UTC File https://tweetkeep.com/data/snaps/2111601904115761286_0.png SHA-256 749d3bdd7a66396c8f13b1e8f7a14af09b5ab62a2193dbfbb73bb8e3b3bc2824 Listed in https://tweetkeep.com/data/proofs/2026-10-18T0019.txt Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-18T0019.txt.ots X's own data for this post, saved by the Internet Archive (Wayback Machine), captured 2026-10-18 00:49 UTC: https://web.archive.org/web/20261018004903/https://cdn.syndication.twimg.com/tweet-result?id=2111601904115761286&token=549sjrknski&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