@phanpp11on X · 2026-10-10
A tamper-evident, on-chain timestamp of what this post said. Captured 2026-10-10 23:13 UTC.
You do not have to chase short term issues. The problem has always been developers. They were kings. They have lost that place someone like myself and there are lots who can now use ai to do the coding. What you need to do is help us plug into the eco system. With that you get the usage and the transaction fees factor that gets more important as we approach April 2028. Plus the Chinese will start mining by next year which means btc price must rise for miners to be profitable or more likely they will switch to chains that offer more fees. Either way the prices will reflect usage rather than hype.
Verify it yourself: the manifest is the exact JSON whose
SHA-256 is 0821a87211f339dfee190d22bf9bd89000c9d67a269115d205b57d3e3fd4e51c; it binds the tweet id, author, post time, and the SHA-256 of the text above. Re-hash the text to match 720caea14c33bcfa42de0ce6d88ecbd9ee46340b8737cf81ecf2d7483b5f29f4, and read the anchor transaction's OP_RETURN
bsv.cx / x1 / 0821a87211f339dfee190d22bf9bd89000c9d67a269115d205b57d3e3fd4e51c — 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.