Tweetkeep proof for X post 2112189119866835252 by @MarioNawfal
https://x.com/MarioNawfal/status/2112189119866835252
First archived 2026-10-19 14:35 UTC

Post text, saved 2026-10-19 14:35 UTC
  File     https://tweetkeep.com/proof/2112189119866835252/text
  SHA-256  10c1c7b5d81ac5ce58673ddcf057ac4851c627c63df21b949e94474ca99f5ad8
  Listed in https://tweetkeep.com/data/proofs/2026-10-19T1512.txt
  Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-19T1512.txt.ots

Page snapshot, saved 2026-10-19 14:36 UTC
  File     https://tweetkeep.com/data/snaps/2112189119866835252_0.png
  SHA-256  b34090f02191a9e4b7e3655ddf07669c6e9e80444492903ce29a82a57b5f0098
  Listed in https://tweetkeep.com/data/proofs/2026-10-19T1512.txt
  Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-19T1512.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-19 15:51 UTC  https://tweetkeep.com/warc/3.warc.gz
    SHA-256  22f99484f1722ab57e18fe87db1a9fb5bf5ed591886cbb1f796236675ad6af88
    Listed in https://tweetkeep.com/data/proofs/2026-10-19T1555.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