Reference
What it does
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 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.
State
Primary objects
| Concept | Definition |
|---|---|
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. |
Messages
Messages & queries
Message and query surfaces are documented at implementation level in the module docs ↗ and the source ↗. The objects above are the state those messages create and transition.
Connections
Module interactions
-
x/veidIdentity submissions are accepted only from approved clients. -
x/rolesConfiguration changes require authorized roles and governance. -
x/issuancepolicyEconomic policy parameters live alongside operational config.
Flows
Core flow
- Propose — A change is proposed. Adding an approved client or adjusting a parameter opens a public governance proposal.
- Vote — Stakeholders decide. The network's stakeholders vote — the trust decision sits with them, not with any single party.
- Store — Config lands in state. The approved list and parameters become queryable chain state that enforcement reads.
- Enforce — Validator checks apply. Identity submissions failing the approved-client and signature checks are rejected before scoring.
Questions
Asked about x/config
What is the approved-client list?
The set of client interfaces permitted to submit identity data into VEID — a governance-vetted list, because the security of the identity pipeline depends on the integrity of capture software.
Why does client approval live on-chain?
It puts the trust decision where it belongs — with the network's stakeholders, under public proposal and vote — rather than with any single party distributing capture apps.
What else is governed here?
Operational parameters across the chain, so configuration is always a queryable, proposal-governed fact — role-authorized and, where required, MFA-protected.
Related