Tweetkeep proof for X post 2111226478671384958 by @MarioNawfal https://x.com/MarioNawfal/status/2111226478671384958 First archived 2026-10-16 22:51 UTC Post text, saved 2026-10-16 22:51 UTC File https://tweetkeep.com/proof/2111226478671384958/text SHA-256 d3498dd639a6bead68d2d57e5b85d2aad7e63210aa33df25764cec38c1bb1693 Listed in https://tweetkeep.com/data/proofs/2026-10-16T2336.txt Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-16T2336.txt.ots Page snapshot, saved 2026-10-16 22:51 UTC File https://tweetkeep.com/data/snaps/2111226478671384958_0.png SHA-256 8f09fd61c7ff3e8f8443dcaf97d9a57d4b348b3178fdda8e2c803a3a2224d187 Listed in https://tweetkeep.com/data/proofs/2026-10-16T2336.txt Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-16T2336.txt.ots X's own data for this post, saved by the Internet Archive (Wayback Machine), captured 2026-10-17 01:18 UTC: https://web.archive.org/web/20261017011852/https://cdn.syndication.twimg.com/tweet-result?id=2111226478671384958&token=548m37wqzh&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