Tweetkeep proof for X post 2114197713340297572 by @MarioNawfal https://x.com/MarioNawfal/status/2114197713340297572 First archived 2026-10-25 03:41 UTC Post text, saved 2026-10-25 03:41 UTC File https://tweetkeep.com/proof/2114197713340297572/text SHA-256 3919fef7dd8c8ea5953a4e4fecfabcc0245183ce9d2250bcafbacde4ff7881f4 Listed in https://tweetkeep.com/data/proofs/2026-10-25T0354.txt Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-25T0354.txt.ots Page snapshot, saved 2026-10-25 06:55 UTC File https://tweetkeep.com/data/snaps/2114197713340297572_0.jpg SHA-256 d4e3953ad5fc0725236e85831da379fbec61fca74a3871252dd69da7f0881013 Not timestamped yet: it goes into the next hourly list 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-25 03:41 UTC https://tweetkeep.com/warc/7982.warc.gz SHA-256 f9d7c4f8122a0b3f3e06c068a25179342ab008d95164471bf1716a1cd8dbe696 Listed in https://tweetkeep.com/data/proofs/2026-10-25T0354.txt 2026-10-25 03:58 UTC https://tweetkeep.com/warc/8005.warc.gz SHA-256 faf260be46fbc1acce5d52994480e96b4c2d72c296efe282a8ec48002923d236 Listed in https://tweetkeep.com/data/proofs/2026-10-25T0454.txt 2026-10-25 04:16 UTC https://tweetkeep.com/warc/8028.warc.gz SHA-256 7184e96e7d959612cf4434fa59ce5931f7146e813c170cd7eb45186723b098ce Listed in https://tweetkeep.com/data/proofs/2026-10-25T0454.txt 2026-10-25 04:32 UTC https://tweetkeep.com/warc/8047.warc.gz SHA-256 5279e6b55a490b44073eb2a36bdae41ed6c2f5fc05659b9ae326752227cec203 Listed in https://tweetkeep.com/data/proofs/2026-10-25T0454.txt 2026-10-25 06:55 UTC https://tweetkeep.com/warc/8227.warc.gz SHA-256 c74f432e64ae6d9fef36bc2e8110a83623a999517a0810b9f8ce9f25f0ae56f1 Not timestamped yet: it goes into the next hourly list 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 . 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 .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