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