Sovereign Services
Identity & Residence
The State's registries record that an identity, a credential or a residence exists and who issued it, so anyone can verify it. They never record the personal details themselves: those stay with the issuer and with the person they belong to.
Issued by Issuers named by governance
Personal data Never on chain, only commitments
Verification By anyone, against the ledger
01 How an identity is recorded
An identity issuer records an identity with its controller account and a commitment: a hash of the person's attributes. The attributes themselves stay with the issuer and the holder. Anyone shown the attributes can check them against the commitment on the ledger, and learns nothing from the ledger alone.
- 1 Created The issuer records the identity, its controller and the attributes commitment.
- 2 Updated The issuer records a new commitment when details change.
- 3 Key rotated The holder moves control to a new key without the issuer.
- 4 Status The issuer can suspend or revoke an identity; the record itself remains.
02 Credentials
IssuingAn issuer issues credentials within the schemas governance gave it, each tied to a position in the issuer's revocation list.
RevokingRevocation flips that position in the issuer's public revocation list, in batches. A verifier checks one bit to know whether a credential still stands.
VerifyingAnyone holding a credential can check its issuer, its schema and its revocation status against the ledger, without asking the issuer.
03 Residence
PermitsA residence issuer records permits in the residence classes it is authorised for, each with its holder and expiry epoch.
ExpiryExpiry is computed from the recorded epoch, never stored separately, so a permit cannot be shown as valid past its date.
HistoryEvery residence change appends a numbered history entry that is never rewritten and can be proven against any block.
04 Who may write what
| Operation | Types | Permitted to |
|---|---|---|
| Create, update, suspend an identity | 48 · 49 · 50 | The identity issuer's controller, within its scope |
| Rotate an identity's key | 51 | The identity's own controller |
| Issue and revoke credentials | 52 · 53 | The issuer's controller, for its schemas |
| Issue and change residence | 56 · 57 | The residence issuer's controller, for its classes |
| Name an issuer | Governance | The council, with a one-epoch notice |
Each operation is permitted to exactly one party, checked before anything changes. A transaction from anyone else is refused and changes nothing.