Seven principles
Seven principles govern every technical choice behind this.
| # | Principle | Meaning |
|---|---|---|
| 1 | Compliance at the protocol layer | Control sits beneath the application layer, so contracts cannot route around it |
| 2 | Private by default, interoperable by intent | Private inside; only what is chosen goes out |
| 3 | Security from identity, not from token price | Validators are known parties, bound by contract, paid in real money |
| 4 | No single party runs everything | By default there is always at least one node outside the operating team |
| 5 | One main path, done properly | Automate exactly one path, and it must work with real customers |
| 6 | Measurable on chain, or non-existent | Published numbers are read from the chain; no dashboard is the source of truth |
| 7 | Inherited genesis | The network is designed to pass through several periods (three testnets, then mainnet); contribution history from earlier periods is preserved and attached to the shared ledger, but no period promises a one-for-one balance |
The seventh principle is one few projects dare to write down, so it needs stating plainly. A network can be rebuilt: to change base parameters, to fix a mistake that cannot be hot-patched, or to move into the next period. The project chooses to announce that in advance rather than let it happen and explain afterwards.
The direct consequence for this document: the network's identity is a live fact, not a constant. That is why you will find no chain identity hard-coded here. Every page points to where the current identity can be read.
What the core refuses to do
A platform is defined as much by what it refuses to do as by its feature list.
Figure 16 — The screening gate stands in front of every sales pitch, and the four things the core refuses.
Refuses to accept the wrong problem. If your problem is one party's internal data, the right answer is a database, and saying so plainly is cheaper for both sides. The three conditions above are a screening test written as a rule, not as advice.
Refuses token-economic security for private customers. The shared-security model means outside validators can see the data. It destroys the very thing customers pay for.
Refuses to issue assets on a customer's behalf. The platform runs chains. Issuers issue their own tokens, and carry their own licences.
Refuses to let one party hold more than a third of voting power. This is not a decentralisation slogan but a mathematical threshold, explained under Security and fault tolerance below. And to be straight about it: this is something the project itself has not passed — as long as the nodes are raised and keyed by one party, the threshold is a rule set for ourselves, not a state achieved. It sits on the open list in Open questions and concerns, exactly where it belongs.
Refuses to touch the price. For LOVE9: no selling, no listing, no price support, no promise of returns.
In short: a customer cannot protect themselves from a platform that accepts everything. The refusal list is what protects them.