@indelibleBSVon X · 2026-08-29
A tamper-evident, on-chain timestamp of what this post said. Captured 2026-09-06 15:24 UTC.
Last night a builder asked me the question I have been building toward for over a year: "How can I build on Indelible today?" Here is the answer, in public, boundaries and all. The system is built like a forest. Underground runs the mycelium: a federation of Bitcoin SV bridges that broadcast, verify, and serve chain truth to anyone. On top grow the trees: the apps. https://t.co/aUAAuMqVjr is a tree. Git hosting on the chain itself is a tree. An Electrum gate serving real wallets is a tree. I planted every one of them myself. There is room for trees I did not plant. That is the whole design. What is open to you today, no permission, no fee, no license: The public bridges, on npm, that put you on Bitcoin with one install. The x402 payment pattern, where the buyer pays the seller's own address and we never custody a sat. The selective disclosure crypto in the shipped CLI, where an encrypted thing unlocks for exactly one buyer. Payments. Storage. Identity. Provenance. The rails are open. Trees grow free. Now the boundary, stated plainly, because you deserve to know where it is before you build: The code carries a Business Source License, and it means one thing. Take my code and stand up a competing service, and you pay me or you ask me. That is the entire restriction. Using the rails is free forever. Cloning the mycelium is what costs. And the honest truth underneath the license: the real moat was never legal. It is a year of running nodes, a sovereign full-history index, and a living forest already growing on top. You cannot fork a world. So I do not need to squeeze builders, and I will not. The forest getting bigger is the whole point. What is coming: an SDK wrapping all of it into one clean onramp. Deep in build. Its verification core already reproduces Bitcoin consensus on real chain data, and every piece is adversarially reviewed before it lands. Not published. No date promised. Builders who show up now will be the first to hold it. If you have a tree in mind, my DMs are open. First come, best soil.
Verify it yourself: the manifest is the exact JSON whose
SHA-256 is 5161777d8847faf173e6eeb1bdc68cd9a2c6f8169690e6c8dcbb53296ac27ef5; it binds the tweet id, author, post time, and the SHA-256 of the text above. Re-hash the text to match 5af93e5a2628bda23d06fcebff90d1146057a10811a280142db859202b25d72d, and read the anchor transaction's OP_RETURN
bsv.cx / x1 / 5161777d8847faf173e6eeb1bdc68cd9a2c6f8169690e6c8dcbb53296ac27ef5 — 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.