Tweetkeep proof for X post 2111181526943817941 by @MarioNawfal https://x.com/MarioNawfal/status/2111181526943817941 First archived 2026-10-16 19:49 UTC Post text, saved 2026-10-16 19:49 UTC File https://tweetkeep.com/proof/2111181526943817941/text SHA-256 09cbfa703b036a2a936d72afc8356654aaf04c5448dd16cb2f4845aa17cc4bcf Listed in https://tweetkeep.com/data/proofs/2026-10-16T2036.txt Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-16T2036.txt.ots Page snapshot, saved 2026-10-16 19:49 UTC File https://tweetkeep.com/data/snaps/2111181526943817941_0.png SHA-256 75589a30f890a1944a38f31b7c4d2b4f71d65a7c13cc96bfec9f8bf8a2026b46 Listed in https://tweetkeep.com/data/proofs/2026-10-16T2036.txt Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-16T2036.txt.ots X's own data for this post, saved by the Internet Archive (Wayback Machine), captured 2026-10-17 02:18 UTC: https://web.archive.org/web/20261017021852/https://cdn.syndication.twimg.com/tweet-result?id=2111181526943817941&token=548h75ckbm&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