🐦 Archived X post

A tamper-evident, on-chain timestamp of what this post said. Captured 2026-10-06 15:09 UTC.

@l3ch00on X · 2026-10-05
@kgonia7 @ALEngineered It’s not vibe coding if the meat proxy starts thinking.
posthttps://x.com/l3ch00/status/2107104255169454565
author id1711788103529107456
posted2026-10-05T13:42:57.000Z
manifest sha25673615ae0371bbefb08904b758f8da01d6209359c7c23696d832df642d9eebfd2
text sha256a8b5f29e39e000ce868a87e2364066f242203ee683212558a01beba26ec03e7d
on-chain⛓ anchored — e03f50741247b064747d56711af3ac50abba37eb81ccb900f8b1136ca4ad5a27

Verify it yourself: the manifest is the exact JSON whose SHA-256 is 73615ae0371bbefb08904b758f8da01d6209359c7c23696d832df642d9eebfd2; it binds the tweet id, author, post time, and the SHA-256 of the text above. Re-hash the text to match a8b5f29e39e000ce868a87e2364066f242203ee683212558a01beba26ec03e7d, and read the anchor transaction's OP_RETURN bsv.cx / x1 / 73615ae0371bbefb08904b758f8da01d6209359c7c23696d832df642d9eebfd2 — 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