Why 9Chain exists
One sentence, and this whole part exists to explain it:
Blockchain should not be a privilege of the few.
In the early period of this technology, opening a blockchain network of your own demanded deep expertise, serious capital and a long road. Those three barriers stop nobody openly — they just quietly leave the right to build digital infrastructure in the hands of a few well-resourced organisations. 9Chain exists to take those barriers down, one step at a time.
Three things, and the order between them means something
| The work | Why it sits here | |
|---|---|---|
| 1 | Create | Opening a chain of your own has to become as ordinary as opening a website. While creating is still hard, the two below have no room to happen |
| 2 | Own | The chain you create is yours: your rules, your governance, your economics. Not rented space on someone else's network, reclaimable whenever they choose |
| 3 | Govern | People should not merely use infrastructure that someone else builds and whose rules someone else changes. This is the hardest of the three, and it comes last because it only means anything once the first two are real |
That order is also the one most often reversed in the telling. A project that says "the community governs" before the community has anything to govern is selling a noun, not a mechanism.
Who the people in this story are
An individual with an idea. A business serving customers and partners. A school recording learning and achievement. A community setting its own rules. A city or a country building infrastructure that fits its own conditions, instead of importing one wholesale from elsewhere.
That list is ordered by who can use it soonest, not by who matters most — and this document states its own uncomfortable half: the individual heads the list but is furthest from the door. The detail is in Nine roles.
Figure 5 — Three pieces of work and the order they must come in. The dashed arrow is where this document is not allowed to draw a solid line: the goal has not been reached.
Three principles that come with it, and one sentence that lowers the claim
Inherit, do not start from zero. 9Chain does not open by denying what already works. It inherits proven technology and carries it forward; a new chain inherits the platform, the tooling and every improvement across the system, so when one part moves forward the rest can follow.
Independent, but not isolated. Each chain sets its own purpose and rules, but chains are not islands — they have to be able to communicate, share data and exchange value. ⚠️ This is a goal, not a description of the present: interoperability on both branches is an unpassed gate — see A1 and C1 side by side.
There is no final version. No release of this technology will be declared finished. A network people depend on has to keep learning, correct itself, and change alongside them.
And the sentence that lowers the claim, because without it everything above reads as advertising: this part says where 9Chain is heading, not how far it has got. Creating a chain on the public test network does work — a few minutes to stand up, and some technical familiarity. Closer to the goal than before, and not there.
In short: an infrastructure project deserves to be measured by the distance between where it stands and where it says it is going, not by how well that destination is phrased. Throughout this document that distance is written out as countable gates — and Risks and open questions is where it is told once more, without softening.
In this part
| Page | What it answers |
|---|---|
| Context and need | The market, three roads, and why the third |
| Nine missions | Nine things the network must answer to |
→ Next: Context and need — The market, three roads, and why the third