Tweetkeep proof for X post 2112633452113670266 by @MarioNawfal https://x.com/MarioNawfal/status/2112633452113670266 First archived 2026-10-20 21:46 UTC Post text, saved 2026-10-20 21:46 UTC File https://tweetkeep.com/proof/2112633452113670266/text SHA-256 00c1016ab6811d51b4f5976d40d17391e367cdef75e2d3f138a7a4c00bda0e9f Listed in https://tweetkeep.com/data/proofs/2026-10-20T2229.txt Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-20T2229.txt.ots Page snapshot, saved 2026-10-20 22:10 UTC File https://tweetkeep.com/data/snaps/2112633452113670266_0.jpg SHA-256 b865b2ee7a7f95fc860c6c174f308cfc84a73c2825c368fd356b4017c0c19ec5 Listed in https://tweetkeep.com/data/proofs/2026-10-20T2229.txt Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-20T2229.txt.ots X's own data for this post as it reached our browser, as WARC records (open with any WARC tool, e.g. https://replayweb.page): 2026-10-20 21:46 UTC https://tweetkeep.com/warc/988.warc.gz SHA-256 b4cdf0dd259d83e7c6510ed67c2ddea436e7c44068f6a6e22e760d4f703240db Listed in https://tweetkeep.com/data/proofs/2026-10-20T2229.txt No Internet Archive copy: we ask it for a few hundred fresh posts a day, from the accounts that delete the most. X's data for every post is in the WARC records above. 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