x/provider — Provider module
The x/provider module is the registry of capacity operators. A provider
record carries the operator’s chain address, service endpoint, and
attributes: region, hardware classes, certifications, and any property a
tenant might filter on when choosing where a workload lands.
Attributes are the connective tissue of marketplace trust. Tenants constrain orders to providers matching required attributes, and auditors can sign attributes (via x/audit) so claims like datacenter tier or jurisdiction carry third-party weight rather than self-assertion alone.
What it does
Section titled “What it does”The module maintains, on-chain:
- The provider record. Address, endpoint, and attributes in one verifiable registration that tenant orders filter against.
- Domain verification. A token-and-challenge flow lets a provider prove control of its service domain, with verification confirmable and revocable on chain.
- Provider signing keys. Operators set, rotate, and revoke the key their daemon signs with, with key epochs queryable for verification history.
Auditor signatures upgrade self-claims into attestations that orders can explicitly require, and published hardware benchmarks tie measured performance to the record so bids compete on evidence.
Why it exists
Section titled “Why it exists”An open marketplace needs a structured, verifiable answer to “who is offering this capacity?”. Registering providers on-chain — with attributes that auditors can attest — replaces the trust role a centralized cloud’s brand plays, using records anyone can verify.
Primary objects
Section titled “Primary objects”| Concept | Definition |
|---|---|
| Provider record | The on-chain registration carrying an operator’s endpoint and attributes. |
| Attribute | A key–value property of a provider — region, hardware, certification — filterable by tenant orders. |
| Provider daemon | The off-chain agent that bids, orchestrates workloads, and reports usage for a registered provider. |
Core flow
Section titled “Core flow”- Verify — VEID verification first. Registration is identity-gated through VEID verification — accountability starts before the first bid.
- Register — Create the record. Address, endpoint, and attributes go on-chain as the provider record tenants will filter against.
- Attest — Get attributes signed. Auditor signatures upgrade self-claims into attestations that tenant orders can explicitly require.
- Benchmark — Publish measurements. Hardware benchmarks tie measured performance to the record, so bids compete on evidence.
Messages
Section titled “Messages”| Message | Purpose |
|---|---|
MsgCreateProvider | Registers a provider record on-chain. |
MsgUpdateProvider | Updates a registered provider’s endpoint and attributes. |
MsgDeleteProvider | Removes a provider record. |
MsgGenerateDomainVerificationToken | Generates a token proving control of the provider’s domain. |
MsgRequestDomainVerification | Starts domain verification for a provider. |
MsgConfirmDomainVerification | Confirms a pending domain verification. |
MsgRevokeDomainVerification | Revokes a previously confirmed domain verification. |
MsgVerifyProviderDomain | Performs a domain verification check for a provider. |
MsgSetProviderSigningKey | Sets the key the provider daemon signs with. |
MsgRotateProviderSigningKey | Rotates the provider’s signing key. |
MsgRevokeProviderSigningKey | Revokes a provider signing key. |
Queries
Section titled “Queries”| Query | Purpose |
|---|---|
Provider / Providers | A single provider record, or the registry list. |
ProviderSigningKey | The current signing key for a provider. |
ProviderSigningKeyEpochs | Past signing-key epochs for a provider. |
Module interactions
Section titled “Module interactions”| Module | How they interact |
|---|---|
| x/market | Bids are placed by registered providers; orders filter on provider attributes. |
| x/audit | Auditors sign provider attributes to upgrade self-claims into attestations. |
| x/benchmark | Published hardware benchmarks are tied to the provider record. |
| x/veid | Provider registration is identity-gated through VEID verification. |
Related documentation
Section titled “Related documentation”- Providers Overview — what it means to operate capacity on the network.
- Provider Daemon — the off-chain agent that bids and orchestrates workloads.
- Benchmarks & Audits — getting claims measured and attested.
- Choosing Providers — how tenants filter on attributes when picking a bid.
- On-Chain Module Map — all 27 modules at a glance.
What is a provider attribute?
Section titled “What is a provider attribute?”A key–value property of a provider — region, hardware class, certification — that tenant orders can filter on when choosing where a workload lands.
Who can sign attributes?
Section titled “Who can sign attributes?”Recognized auditors via x/audit. Auditor status is itself an on-chain
role, and attestations are revocable and traceable to accountable,
identity-verified signers. See the x/audit module.
What is the provider daemon?
Section titled “What is the provider daemon?”The off-chain agent that watches open orders, bids per configured pricing, instantiates won leases on the operator’s infrastructure, meters usage per workload, and submits signed records to the chain.