Tweetkeep proof for X post 2110874611537920372 by @MarioNawfal https://x.com/MarioNawfal/status/2110874611537920372 First archived 2026-10-15 23:34 UTC Post text, saved 2026-10-15 23:34 UTC File https://tweetkeep.com/proof/2110874611537920372/text SHA-256 76ca9ec4c1b50804c13bf5522d1e1372ae273a43e84659da76b9facad6e51ed7 Listed in https://tweetkeep.com/data/proofs/2026-10-16T0014.txt Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-16T0014.txt.ots Page snapshot, saved 2026-10-15 23:36 UTC File https://tweetkeep.com/data/snaps/2110874611537920372_0.png SHA-256 0f3c237f2f72a8d5e11511e50e50ea838ec9b08325bc2b11474b72ec87ff9511 Listed in https://tweetkeep.com/data/proofs/2026-10-16T0014.txt Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-16T0014.txt.ots X's own data for this post, saved by the Internet Archive (Wayback Machine), captured 2026-10-16 00:38 UTC: https://web.archive.org/web/20261016003856/https://cdn.syndication.twimg.com/tweet-result?id=2110874611537920372&token=547iala9445&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