Tweetkeep proof for X post 2102503492174643683 by @gidonsaar
https://x.com/gidonsaar/status/2102503492174643683
First archived 2026-10-20 06:27 UTC

Post text, saved 2026-10-20 06:27 UTC
  File     https://tweetkeep.com/proof/2102503492174643683/text
  SHA-256  52fdfbfef10bd4938e9f4a459fdccd70de741e64d78074d77e09e9197fc57ac9
  Listed in https://tweetkeep.com/data/proofs/2026-10-20T0629.txt
  Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-20T0629.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-20 06:27 UTC  https://tweetkeep.com/warc/464.warc.gz
    SHA-256  d618ebebd83d1bcbcf71db4d9b5af8e1773235f0772d20947f5a98a158225bca
    Listed in https://tweetkeep.com/data/proofs/2026-10-20T0629.txt
  2026-10-20 11:34 UTC  https://tweetkeep.com/warc/666.warc.gz
    SHA-256  19e43bef8a4dd6e91d5e49f20ff8dc2b80dd44e1d5668caded750f44c05f278b
    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 <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