Tweetkeep proof for X post 2112672709859574145 by @MarioNawfal
https://x.com/MarioNawfal/status/2112672709859574145
First archived 2026-10-20 23:02 UTC

Post text, saved 2026-10-20 23:02 UTC
  File     https://tweetkeep.com/proof/2112672709859574145/text
  SHA-256  f71d7698c9a138ee7dba61ac424a7e1346a7fe54143f25c033eee2caa3993d9e
  Listed in https://tweetkeep.com/data/proofs/2026-10-20T2329.txt
  Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-20T2329.txt.ots

Page snapshot, saved 2026-10-20 23:11 UTC
  File     https://tweetkeep.com/data/snaps/2112672709859574145_0.jpg
  SHA-256  b865b2ee7a7f95fc860c6c174f308cfc84a73c2825c368fd356b4017c0c19ec5
  Listed in https://tweetkeep.com/data/proofs/2026-10-20T2329.txt
  Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-20T2329.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 23:02 UTC  https://tweetkeep.com/warc/1050.warc.gz
    SHA-256  4a638dd5a4920290b9d4d5e96f89a47079a2ac7f44e905cda6af7da99f2f070e
    Listed in https://tweetkeep.com/data/proofs/2026-10-20T2329.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