Tweetkeep proof for X post 2113290242363158710 by @MarioNawfal
https://x.com/MarioNawfal/status/2113290242363158710
First archived 2026-10-23 05:57 UTC

Post text, saved 2026-10-23 05:57 UTC
  File     https://tweetkeep.com/proof/2113290242363158710/text
  SHA-256  00601fba9ad8f18e8df0187ad708968606a45deaa1cde7e9a4feb132b04e136e
  Listed in https://tweetkeep.com/data/proofs/2026-10-23T0654.txt
  Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-23T0654.txt.ots

Text after the edit, saved 2026-10-23 15:24 UTC
  File     https://tweetkeep.com/proof/2113290242363158710/edit
  SHA-256  f2e028aaca82841fbd1b8204f89515b14a9af7c4b4b25332285e54a17d2dd5c4
  Listed in https://tweetkeep.com/data/proofs/2026-10-23T1554.txt
  Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-23T1554.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-23 05:57 UTC  https://tweetkeep.com/warc/4182.warc.gz
    SHA-256  b71246bd204f8e86e07dd4658a62589ca2e55977e9e402320c3571705c22a665
    Listed in https://tweetkeep.com/data/proofs/2026-10-23T0654.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