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

Post text, saved 2026-10-20 21:46 UTC
  File     https://tweetkeep.com/proof/2112637478322700601/text
  SHA-256  ca02c67a7419e157569bf864b2f41a15b3a700da6e4e091756be5bd319cc37a3
  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:04 UTC
  File     https://tweetkeep.com/data/snaps/2112637478322700601_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 <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