Tweetkeep proof for X post 2110907961375859179 by @MarioNawfal https://x.com/MarioNawfal/status/2110907961375859179 First archived 2026-10-16 01:51 UTC Post text, saved 2026-10-16 01:51 UTC File https://tweetkeep.com/proof/2110907961375859179/text SHA-256 687f291c5aba21029ac6690f5df28cf8e6d8e12107681870e3144c9373009464 Listed in https://tweetkeep.com/data/proofs/2026-10-16T0214.txt Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-16T0214.txt.ots Page snapshot, saved 2026-10-16 01:54 UTC File https://tweetkeep.com/data/snaps/2110907961375859179_0.png SHA-256 788c30bbb5afe4ab1421c71216e9f993da32e9bf523831d9db9bce8da62d0983 Listed in https://tweetkeep.com/data/proofs/2026-10-16T0214.txt Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-16T0214.txt.ots X's own data for this post, saved by the Internet Archive (Wayback Machine), captured 2026-10-16 01:56 UTC: https://web.archive.org/web/20261016015607/https://cdn.syndication.twimg.com/tweet-result?id=2110907961375859179&token=547m2dibh2w&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