Tweetkeep proof for X post 2110525093516316865 by @MarioNawfal https://x.com/MarioNawfal/status/2110525093516316865 First archived 2026-10-15 00:18 UTC Post text, saved 2026-10-15 00:18 UTC File https://tweetkeep.com/proof/2110525093516316865/text SHA-256 d66523474d46661d5ac6d88eec2e3d723917548ebbfd02371dda43f435d31871 Listed in https://tweetkeep.com/data/proofs/2026-10-15T0041.txt Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-15T0041.txt.ots Page snapshot, saved 2026-10-15 00:18 UTC File https://tweetkeep.com/data/snaps/2110525093516316865_0.png SHA-256 dd53292ea05c71d6aee4b463a3668bddff9cbec940067c29f76a6467b6536a77 Listed in https://tweetkeep.com/data/proofs/2026-10-15T0041.txt Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-15T0041.txt.ots X's own data for this post, saved by the Internet Archive (Wayback Machine), captured 2026-10-15 00:48 UTC: https://web.archive.org/web/20261015004818/https://cdn.syndication.twimg.com/tweet-result?id=2110525093516316865&token=546eriz8rlj&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