Governance and infrastructure
A register for securities is long-lived infrastructure. The assets it records can outlast many versions of the software that records them. The protocol has to be governable, so that it is always clear who may do what, and it has to evolve without putting the register at risk.
This section describes the infrastructure that serves both: one access model for every privileged action, standard mechanisms for upgrades, deterministic addresses across chains, and a storage layout that survives upgrades. Each is built from a standard mechanism in preference to a bespoke one.
The AccessManager model, how roles are scoped to domains, how a suite is commissioned, and who administers what.
What is upgradeable and by whom, shared and isolated suites, published versions, and the safeguards of an upgrade.
Addresses that depend only on the factory and a salt: one address per asset and per identity across EVM chains, and contracts wired to each other at deployment.
How each layer keeps its state in its own region, the namespaces of the protocol, and what that protects in an upgrade.
Last updated