Tweetkeep proof for X post 2110407732259881079 by @MarioNawfal https://x.com/MarioNawfal/status/2110407732259881079 First archived 2026-10-14 16:42 UTC Post text, saved 2026-10-14 16:42 UTC File https://tweetkeep.com/proof/2110407732259881079/text SHA-256 23b30843b6c1d66db814265da3c3ff60980a9354b235ae936a1a6b237f6b8582 Listed in https://tweetkeep.com/data/proofs/2026-10-14T1741.txt Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-14T1741.txt.ots Page snapshot, saved 2026-10-14 16:43 UTC File https://tweetkeep.com/data/snaps/2110407732259881079_0.png SHA-256 fec4e88548c4e88502f703db00f0659d26aa11592a42f1312ced6529374ed921 Listed in https://tweetkeep.com/data/proofs/2026-10-14T1741.txt Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-14T1741.txt.ots X's own data for this post, saved by the Internet Archive (Wayback Machine), captured 2026-10-15 03:41 UTC: https://web.archive.org/web/20261015034152/https://cdn.syndication.twimg.com/tweet-result?id=2110407732259881079&token=5461houpfbg&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