Tweetkeep proof for X post 2112404606089072785 by @MarioNawfal
https://x.com/MarioNawfal/status/2112404606089072785
First archived 2026-10-20 06:31 UTC

Post text, saved 2026-10-20 06:31 UTC
  File     https://tweetkeep.com/proof/2112404606089072785/text
  SHA-256  0e55bc881d0f1fddd8acf636d480ff1fd9bb8f9c72709cd6517ebb4adba5c444
  Listed in https://tweetkeep.com/data/proofs/2026-10-20T0729.txt
  Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-20T0729.txt.ots

Page snapshot, saved 2026-10-20 06:58 UTC
  File     https://tweetkeep.com/data/snaps/2112404606089072785_0.jpg
  SHA-256  b865b2ee7a7f95fc860c6c174f308cfc84a73c2825c368fd356b4017c0c19ec5
  Listed in https://tweetkeep.com/data/proofs/2026-10-20T0729.txt
  Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-20T0729.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 06:31 UTC  https://tweetkeep.com/warc/469.warc.gz
    SHA-256  69307d4a0754eb55ec6c345e4f23f2e4a2129511e04066e2f20a8ea9a1ace6d2
    Listed in https://tweetkeep.com/data/proofs/2026-10-20T0729.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 <file>. 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 <list>.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