Tweetkeep proof for X post 2111190630869201380 by @sneako
https://x.com/sneako/status/2111190630869201380
First archived 2026-10-16 20:37 UTC

Post text, saved 2026-10-16 20:37 UTC
  File     https://tweetkeep.com/proof/2111190630869201380/text
  SHA-256  89086be3d7d35414bca3c135f49d80bc4e28119d0db226f80376d36f0079e111
  Listed in https://tweetkeep.com/data/proofs/2026-10-16T2136.txt
  Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-16T2136.txt.ots

Page snapshot, saved 2026-10-16 20:37 UTC
  File     https://tweetkeep.com/data/snaps/2111190630869201380_0.png
  SHA-256  004cc4b072a6b56176fcd3ca6d495cec6ae3df8bac591d5edd4577206ffb20b0
  Listed in https://tweetkeep.com/data/proofs/2026-10-16T2136.txt
  Bitcoin timestamp of that list: https://tweetkeep.com/data/proofs/2026-10-16T2136.txt.ots

X's own data for this post, saved by the Internet Archive (Wayback Machine), captured 2026-10-17 02:13 UTC:
  https://web.archive.org/web/20261017021341/https://cdn.syndication.twimg.com/tweet-result?id=2111190630869201380&token=548i19jr37a&lang=en

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