This is a strategic move, not a gamble — and the distinction is worth making in the very first line. A gamble stakes something on what you do not know, and then waits. Building both foundations is the opposite: it costs twice over precisely so that nothing has to be guessed. It moves a decision that is close to irreversible — which engine carries this platform for years — off judgement and onto a measurement anyone can reproduce. The price is paid in money and time; what it buys is not having to rely on luck.

9Chain is being built twice at the same time, on two independent technical foundations, and the community will choose which foundation becomes the official network. The two branches are called 9Chain A1 and 9Chain C1. Throughout this document they are always listed in alphabetical order, and that order implies no ranking — it is a rule of the project, not a courtesy.

Why build the same thing twice

The choice of the engine underneath decides what the platform can do for years, and it is the kind of decision that is close to irreversible once people have built on top. There are two ways to make it: read the documentation of both technologies and argue, or stand both up and measure. The first is far cheaper and ends with whichever side argues better winning. The second costs twice as much and ends with a number anyone can reproduce.

The project chose the second. That is why two public test networks run side by side, each exposing the same set of public surfaces: an endpoint, an explorer, a test faucet, and a path to create a sovereign chain. A comparison only means something when both sides expose the same things.

What this means for you

If you are	What to do	What not to do
Reading to understand	read both, and take the alphabetical order exactly as it is	conclude that either branch is "the official one" — neither is
Building experimentally	try both; the public endpoints exist precisely for this	pick one branch and build something you need to keep on it
Planning to operate	read the technical documentation published by that branch itself	assume the two branches share one set of commands

And one thing common to all three: both are test networks, so neither is a commitment to run for real. Balances there carry no value, and a test network can be rebuilt from scratch.

In short: the two branches are not two competing products but one question asked twice, so that it can be answered by measurement instead of by argument. Until the measurements are published and the ballot opens, anyone telling you which branch will win is guessing — including people inside the project.

Diagram

flowchart TB Q["ONE QUESTION which engine should carry this platform for years to come?"] Q --> A["Answer by ARGUMENT read both technologies' docs and debate"] Q --> B["Answer by MEASUREMENT stand both up and measure"] A --> A2["Cheap. Ends with whichever side argues better winning"] B --> B2["Twice the cost. Ends with a number anyone can reproduce"] B2 --> C["The project chose this path"]

Figure 11 — The project's strategic move in one choice: pay twice over to take luck out of a decision that is close to irreversible.

In this part

Page	What it answers
A1 and C1 side by side	Where the branches differ, as trade-offs
Measurement and the ballot	The three gates standing before the ballot

→ Next: A1 and C1 side by side — Where the branches differ, as trade-offs