9Chain Documentation

A ledger of your own, and a shared network so those ledgers can trust one another — something only a few have ever had, now open to anyone.

This document is written in the permanent tense: it describes design, mechanisms, and the gates a network must pass. It is not a snapshot. Every live measurement lives in “Check the network yourself”.

Summary

Ever since people learned to keep records, every society has built a ledger — and for all those centuries the ledger has belonged to someone else. 9Chain makes having a ledger of your own something anyone can reach: an institution, a community, or a single person. In the technology of one era, that ledger takes the shape of a blockchain of its own.

So what is being built is not a ledger, but the machine that produces them: you declare one in words, and the infrastructure raises it, keeps it alive, and takes it down when its work is done. Every ledger born this way carries two things that an old-style corporate ledger does not have and a public ledger will not give: rules enforced inside the consensus mechanism itself rather than in a contract running on top of it, and a controlled, public economic exit. The specific implementation — an operator that raises chains automatically, a console to drive it, an AI layer that turns a description into a working blueprint — is the method of one era, not a definition: when the technology changes, the method changes; those three jobs do not.

The shape of the whole system is therefore multi-chain: many private chains, and one shared network so they can trust each other. That shared network is 9Chain itself, a public blockchain with the native token LOVE9.

The unusual claim sits here: if everyone needs a chain in order to work alongside AI, chains become abundant, and the scarce thing is no longer one more chain — it is a verifiable identity that works across all of them. LOVE9 proposes a total supply of 81 billion, with no allocation to the team, no allocation to investment funds, no premine, and no sale to anyone.

Two self-limiting sentences, placed right here. What this document claims is architecture and mechanism, not operating scale. And every economic number is an opening proposal for the community to vote on, not a commitment — the project's own constitution says so.

And a third sentence, the most important one for a first-time reader: everything in this document was built and proposed by the founding group — not one line has been through a community vote. They stay open: anything not marked ENGRAVED can be changed through public argument and then a vote, and no line is engraved before mainnet — the project passes through three testnet periods first, each one a chance to put this very document to the test and correct it. Before you read defines the four labels used consistently throughout; Conclusion explains how to take part — and lists the doors still closed.

Four ways to read this, depending on who you are

The document has four parts, ordered along one line of reasoning: why it exists → what it promises → how it is built → who is inside → money and power → checking it yourself and taking part. You do not need to read all of it, and you should not read it front to back if you arrived with a specific question.

The fourth path is the one we hope you take. An infrastructure document is only worth reading on if it survives the harshest reader, and the four pages on that path are the four that name what the project still lacks.

In short: what 9Chain builds is not a blockchain, but the right to keep your own ledger — something every generation before had to ask someone else to hold. The entire value of that promise rests on the fact that every sentence above can be checked.