PezkuwiChain is a relay chain with system chains attached to it. The relay provides shared
security and finality; each system chain carries one function of the state and nothing else.
This is not a scaling decision. It is a separation-of-powers decision expressed as
topology: the chain that holds the register is not the chain that holds the money, and
neither is the chain that produces blocks.
| Chain |
Id |
Carries |
| Pezkuwichain (relay) |
— |
Consensus, finality, the validator session, cross-chain routing, and the HEZ escrow |
| Asset Hub |
1000 |
Every fund. PEZ, wHEZ and wUSDT. Staking and validator elections. |
| People |
1004 |
The citizen register, every office, the courts, trust, and the validator pool |
| Bridge Hub |
1002 |
Bridges to other consensus systems, including Ethereum |
| Coretime |
1005 |
Blockspace allocation |
The relay schedules exactly two cores at genesis, one for the Asset Hub and one for People —
the two chains a state cannot run without.
2.1 The one door into the relay's root
The relay chain has no root governance track. There is no referendum that can dispatch as
root, and no collective that can. Root arrives from exactly one place: a message from the
People chain, carried as OriginKind::Superuser, converted by a single origin converter
that matches that chain's identifier and nothing else.
This is the constitutional core of the design, and it is eleven lines of code. The consensus
layer is subordinate to the civil layer, structurally, and no amount of stake on the relay
can reverse the direction.
