Module reference · Identity & security
x/veidregistry — VEID Registry
The registry of identity records and scopes that other modules resolve against.
What it does
Inside x/veidregistry
The veidregistry module is the ledger's index of identity state: which accounts have verified records, which scopes those records comprise, and how identity state is looked up by the modules that enforce identity gates.
Splitting the registry from the scoring engine keeps long-lived identity records cleanly separated from the verification workflow — scoring logic can evolve while the record-of-record interface other modules depend on stays stable.
Why it exists
The design rationale
Every identity-gated action on the chain — registering a provider, creating a deployment, casting an identity-weighted vote — needs a fast, canonical answer to "what is this account's verified identity state?". The registry is that answer, kept apart from the machinery that produces it.
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
Consensus-committed scores and scope outcomes are recorded into the registry.
- x/market
Marketplace identity gates resolve accounts through the registry.
- x/provider
Provider registration checks registry state before admitting operators.
- x/roles
Role assignments can be conditioned on registry-verified identity.
Key concepts
Terms that matter here
- Identity record
- The canonical on-chain record binding an account to its verification outcomes.
- Scope registration
- The registry entry tracking which identity scopes an account has verified.
Keep exploring