Tweetkeep proof for X post 2114402860452716672 by @MarioNawfal https://x.com/MarioNawfal/status/2114402860452716672 First archived 2026-10-25 17:18 UTC Post text, saved 2026-10-25 17:18 UTC File https://tweetkeep.com/proof/2114402860452716672/text SHA-256 8994a80a212d18a19cf8250b13671b680b7e28a56d23e98892bc3086df745f09 Listed in https://tweetkeep.com/data/proofs/2026-10-25T1754.txt Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-25T1754.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-25 17:17 UTC https://tweetkeep.com/warc/9047.warc.gz SHA-256 2edc52f11ea9483c08267682e020a83b747217cc18167b89aeb4b8584876cf0e Listed in https://tweetkeep.com/data/proofs/2026-10-25T1754.txt 2026-10-25 17:34 UTC https://tweetkeep.com/warc/9070.warc.gz SHA-256 3889dd83585857d909155e66616899a6887516d29d275bc396f1e1a60950c114 Listed in https://tweetkeep.com/data/proofs/2026-10-25T1754.txt 2026-10-25 17:51 UTC https://tweetkeep.com/warc/9091.warc.gz SHA-256 649885b8b346fc2739e57c109b5d2937043a7d2e7e6db5f24bc9224d82aee62c Listed in https://tweetkeep.com/data/proofs/2026-10-25T1754.txt 2026-10-25 18:09 UTC https://tweetkeep.com/warc/9113.warc.gz SHA-256 59fb0e1256c0bedc100e70fe780aeb0708c03de4fc3be6f1ce311b908bbfb504 Listed in https://tweetkeep.com/data/proofs/2026-10-25T1854.txt 2026-10-25 18:25 UTC https://tweetkeep.com/warc/9134.warc.gz SHA-256 2e09477e891b6ee736b4afc3450386ee1bb885b93a2bb1c06ad851643791da5c Listed in https://tweetkeep.com/data/proofs/2026-10-25T1854.txt 2026-10-25 18:43 UTC https://tweetkeep.com/warc/9160.warc.gz SHA-256 600d52ad4ea4353c3b88d30c5cfef10f332741db55015d6d1dea83f28530412b Listed in https://tweetkeep.com/data/proofs/2026-10-25T1854.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 . 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