Tweetkeep proof for X post 2111185410017669545 by @MarioNawfal https://x.com/MarioNawfal/status/2111185410017669545 First archived 2026-10-16 20:04 UTC Post text, saved 2026-10-16 20:04 UTC File https://tweetkeep.com/proof/2111185410017669545/text SHA-256 dc39ce16a7ad7726f86df06d01c2ce9ea69f1b0a6fa4ff3f7945844d884a0c10 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 20:04 UTC File https://tweetkeep.com/data/snaps/2111185410017669545_0.png SHA-256 ac21ce81021ec2b7a31a04f4a5c2179b87e1d12f27c5a1488d20295986fd4221 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:16 UTC: https://web.archive.org/web/20261017021623/https://cdn.syndication.twimg.com/tweet-result?id=2111185410017669545&token=548hgb1nx&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