Tweetkeep proof for X post 2113034386253795700 by @MarioNawfal
https://x.com/MarioNawfal/status/2113034386253795700
First archived 2026-10-22 01:59 UTC

Post text, saved 2026-10-22 01:59 UTC
  File     https://tweetkeep.com/proof/2113034386253795700/text
  SHA-256  73c7f829abf3329a73fca4e06f174431a7f319220c6e16b72c1f6b59fc89fcf6
  Listed in https://tweetkeep.com/data/proofs/2026-10-22T0258.txt
  Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-22T0258.txt.ots

Page snapshot, saved 2026-10-22 03:20 UTC
  File     https://tweetkeep.com/data/snaps/2113034386253795700_0.jpg
  SHA-256  b865b2ee7a7f95fc860c6c174f308cfc84a73c2825c368fd356b4017c0c19ec5
  Listed in https://tweetkeep.com/data/proofs/2026-10-22T0358.txt
  Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-22T0358.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-22 01:59 UTC  https://tweetkeep.com/warc/2086.warc.gz
    SHA-256  0afda43e7188047e62449a1318bb67b9c34a5bc54f7176f4ee95516b499aa63c
    Listed in https://tweetkeep.com/data/proofs/2026-10-22T0258.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