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