Tweetkeep proof for X post 2111579276046659966 by @MarioNawfal https://x.com/MarioNawfal/status/2111579276046659966 First archived 2026-10-17 22:07 UTC Post text, saved 2026-10-17 22:07 UTC File https://tweetkeep.com/proof/2111579276046659966/text SHA-256 2befbef3ce03a229f9e7f591c5030df8adcd06635e6acdab0aeaaf3af25ab209 Listed in https://tweetkeep.com/data/proofs/2026-10-17T2219.txt Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-17T2219.txt.ots Page snapshot, saved 2026-10-17 22:08 UTC File https://tweetkeep.com/data/snaps/2111579276046659966_0.png SHA-256 955f9d983f36018caa893212d5fe45d0dcd5f7129f879a2ed16ce05040bb92ad Listed in https://tweetkeep.com/data/proofs/2026-10-17T2219.txt Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-17T2219.txt.ots X's own data for this post, saved by the Internet Archive (Wayback Machine), captured 2026-10-18 01:29 UTC: https://web.archive.org/web/20261018012942/https://cdn.syndication.twimg.com/tweet-result?id=2111579276046659966&token=549pzmvtni7&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