Module reference · Quality & governance
x/config — Config
Governed chain-level configuration — including the approved-client list.
What it does
Inside x/config
The config module holds chain-level configuration as governed state. Its highest-stakes entry is the approved-client list: the set of client interfaces permitted to submit identity data into VEID. Validators verify that identity submissions originate from an approved client and carry the user's signature before scoring them.
Other operational parameters live here too, so that "how the chain is configured" is always a queryable, proposal-governed fact rather than an operator convention.
Why it exists
The design rationale
The security of the identity pipeline depends on the integrity of capture software. Governing the approved-client list on-chain puts that trust decision where it belongs — with the network's stakeholders, under public proposal and vote — instead of with any single party.
Interactions
How it connects to the rest of the chain
No module stands alone — these are the protocol surfaces this module depends on or serves.
- x/veid
Identity submissions are accepted only from approved clients.
- x/roles
Configuration changes require authorized roles and governance.
- x/issuancepolicy
Economic policy parameters live alongside operational config.
Key concepts
Terms that matter here
- Approved client
- A governance-vetted client interface permitted to submit identity data.
- Governed parameter
- A configuration value changeable only by on-chain proposal and vote.
Keep exploring