@BenGrahamUKon X · 2026-09-22
A tamper-evident, on-chain timestamp of what this post said. Captured 2026-09-24 05:19 UTC.
For years, I didn’t take much notice of the small boat crossings. But once you start looking into even the smallest details, you realise just how organised the whole operation around them is. The boats enter the Channel and vessels are waiting to support them. They reach land and coaches are ready to take people away. Then, if a protest appears, huge numbers of police suddenly seem to be available. Just look at the number of police cars here. The scale of resources being thrown at this is staggering.
The scale of this is increasing. Scary. https://t.co/1CJPdAhdyj
This post quote-tweets the one above. Its text and identity are anchored (one level, no deeper); any media it showed is anchored with this post's media. Quoted text may be truncated for a long-form original — the anchored hash covers exactly the text shown here.
Verify it yourself: the manifest is the exact JSON whose
SHA-256 is c9e618541c8ebcbf6568df9d3e62f4e5db9ab28d278571af3bc0fe3a35e752fd; it binds the tweet id, author, post time, and the SHA-256 of the text above. Re-hash the text to match e3b13cb9d5e085d9973ce6726de65506226bf414b6a54cc3f3f64fa3d021c42b, plus the quoted post's id, author, and text hash 818db13c0c6d12c12a7aef5e2eab0eb28d02eb8458e80dec2783ef1758f2c52b, and read the anchor transaction's OP_RETURN
bsv.cx / x1 / c9e618541c8ebcbf6568df9d3e62f4e5db9ab28d278571af3bc0fe3a35e752fd — 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.