Module reference · Marketplace & workloads
x/provider — Provider
Provider registration and the on-chain attribute record tenants filter against.
What it does
Inside x/provider
The 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.
Why it exists
The design rationale
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.
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/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.
Key concepts
Terms that matter here
- 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.
Keep exploring