Architecture
The same system, described three times at increasing resolution. Stop after the first pass and you still have the rules.
Pass one — four tiers
The four tiers below are deliberately unnumbered, because numbers get misread as the industry's Layer 0/1/2 scale — two entirely different schemes. Where 9Chain stands on that scale is covered in Context.
| Tier | What it is | Technology |
|---|---|---|
| Chain base | The blockchain framework | Cosmos SDK, Cosmos EVM, CometBFT |
| Chains produced | What the customer receives | A private EVM appchain with a compliance gate, charging users nothing, connected for interoperability |
| The chain-producing machine | What raises them | A Kubernetes operator, provisioning API, console, key store, explorer, relayer |
| The shared network — 9Chain | The public blockchain where identity · governance · value live in common for every chain | native token LOVE9, kept entirely separate from customer chains' fuel |
The last tier is the one most easily forgotten when people describe a chain-producing machine — and drop it, and what remains is merely an infrastructure service. Multi-chain without a shared network is just many islands. The part immediately below explains why.
The boundary between the shared network tier and the other three is a design decision, not an accident of arrangement: the shared network's token is never a condition for a customer chain to function. Customers pay in real money, and their chain runs regardless of what the token is worth, including when it is worth nothing.
Pass two — the life of a chain
A chain is a declaration. The operator reads that declaration and keeps returning the system to the state described, over and over.
Figure 17 — A self-levelling loop. Every pass gives the same result however many times it runs, so restarting the operator is always safe.
The hardest step is assembling genesis: generating each validator's key into the key store, creating accounts, placing validators directly into genesis, setting base parameters, then verifying before writing. A wrong genesis cannot be patched; it can only be fixed by rebuilding the whole network.
Pass three — many customers on the same infrastructure
Figure 18 — The responsibility boundary: the operator manages only the platform's nodes.
Customer and audit nodes run outside, on their own infrastructure; the operator only produces the artefacts they need to join. That is what makes "multi-party" real rather than decorative — if every node is run by one party, the phrase means nothing.
In short: once the life of a chain is written as code, "running a blockchain" stops being an infrastructure project. It becomes a line of configuration that can be put through review.