Tweetkeep proof for X post 2112982255651922363 by @MarioNawfal
https://x.com/MarioNawfal/status/2112982255651922363
First archived 2026-10-21 21:25 UTC

Post text, saved 2026-10-21 21:25 UTC
  File     https://tweetkeep.com/proof/2112982255651922363/text
  SHA-256  e02d8ca20ffcfee60e53b0a2bfc85f2d89bd2508c657a1460235bd687674458e
  Listed in https://tweetkeep.com/data/proofs/2026-10-21T2158.txt
  Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-21T2158.txt.ots

Page snapshot, saved 2026-10-21 22:09 UTC
  File     https://tweetkeep.com/data/snaps/2112982255651922363_0.jpg
  SHA-256  b865b2ee7a7f95fc860c6c174f308cfc84a73c2825c368fd356b4017c0c19ec5
  Listed in https://tweetkeep.com/data/proofs/2026-10-21T2258.txt
  Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-21T2258.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-21 21:24 UTC  https://tweetkeep.com/warc/1916.warc.gz
    SHA-256  fa5d2445c76c1cf0357643dd828cc3e6b37e38c3ad540f09391d7bc5ee9052f8
    Listed in https://tweetkeep.com/data/proofs/2026-10-21T2158.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