🐦 Archived X post

A tamper-evident, on-chain timestamp of what this post said. Captured 2026-09-13 19:11 UTC.

@Opcode_Networkon X · 2026-09-13

archived media

@twetchapp While that is true, the hijacked ultimately was finished through their proxy blockstream. Be careful tho, scammers like this ☝️ twetchapp account use it to steer people towards their scamcoin (BSV in this case). https://t.co/aCm3atQSsv
posthttps://x.com/Opcode_Network/status/2099182239850299583
author id1290744593206706178
posted2026-09-13T17:03:41.000Z
manifest sha256e3554cfd60c424b169f78ba202d439baf7eeac558a3de45ddfe043d0adf504df
text sha2566b64531d4a4e01f064794cac3bc2e5b4d1e72a8125955c665395f7ee57649158
media sha256f2236943fe111a9c29b7a71ae73a432846c35c3d67f6733091ffb352fd6777af (photo, 91892 bytes)
on-chain⛓ anchored — a89b2871e5ea947474b286b828fd86bfdfabb2cc6fabe0fdaa11c26eaa7437b4

Verify it yourself: the manifest is the exact JSON whose SHA-256 is e3554cfd60c424b169f78ba202d439baf7eeac558a3de45ddfe043d0adf504df; it binds the tweet id, author, post time, and the SHA-256 of the text above. Re-hash the text to match 6b64531d4a4e01f064794cac3bc2e5b4d1e72a8125955c665395f7ee57649158, and read the anchor transaction's OP_RETURN bsv.cx / x1 / e3554cfd60c424b169f78ba202d439baf7eeac558a3de45ddfe043d0adf504df — the block's timestamp proves the post said this at or before that time, with no trust in bsv.cx. Content archived via the X API.

← bsv.cx · JSON · ⚠ Report