Tweetkeep proof for X post 2110298909885300991 by @whatdotcd
https://x.com/whatdotcd/status/2110298909885300991
First archived 2026-10-14 09:56 UTC

Post text, saved 2026-10-14 09:56 UTC
  File     https://tweetkeep.com/proof/2110298909885300991/text
  SHA-256  cc183ff18ee4ffb7a08f6d4e3276c9a569c4d14a292707728da4d0f23ca87407
  Listed in https://tweetkeep.com/data/proofs/2026-10-14T0959.txt
  Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-14T0959.txt.ots

Page snapshot, saved 2026-10-14 09:56 UTC
  File     https://tweetkeep.com/data/snaps/2110298909885300991_0.png
  SHA-256  0caa910976dfb12fed7237d9440db3b482e03073891c4025e6df0a2a2d738456
  Listed in https://tweetkeep.com/data/proofs/2026-10-14T0959.txt
  Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-14T0959.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 16:32 UTC  https://tweetkeep.com/warc/65.warc.gz
    SHA-256  811a05ec69d2f1ad8d1a0e7911b33e40b090a759576066481b3087d0d47f36ef
    Listed in https://tweetkeep.com/data/proofs/2026-10-19T1702.txt
  2026-10-19 17:32 UTC  https://tweetkeep.com/warc/152.warc.gz
    SHA-256  8d2d007938a0f698ac850f3ce508e331fee78d6c9762f3fcaaec5059c39fc0d3
    Listed in https://tweetkeep.com/data/proofs/2026-10-19T1747.txt
  2026-10-19 18:32 UTC  https://tweetkeep.com/warc/245.warc.gz
    SHA-256  8529089ae4395c5674e1f5c2e570835326faf1cbfcb35af92f70057505b89973
    Listed in https://tweetkeep.com/data/proofs/2026-10-19T1847.txt
  2026-10-20 05:31 UTC  https://tweetkeep.com/warc/429.warc.gz
    SHA-256  48a2cf960975a88f24835c371751c2b8ac5c2ac121b62e818e47f109cabcc4cb
    Listed in https://tweetkeep.com/data/proofs/2026-10-20T0629.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