Module reference · Marketplace & workloads
x/resources — Resources
Shared resource-unit and capacity definitions used across the marketplace.
What it does
Inside x/resources
The resources module defines the vocabulary of the marketplace: what a unit of CPU, memory, storage, or GPU means, how capacity is expressed, and how resource requirements are compared for matching. Every module that talks about capacity — deployments, orders, bids, usage records — uses these shared definitions.
Centralizing the resource model prevents drift: a bid can be checked against an order, and a usage record against a lease, because all three quantify resources identically.
Why it exists
The design rationale
Marketplaces fail on ambiguity. If tenant and provider disagree on what "one unit of compute" means, matching and settlement both break. A single, consensus-maintained resource model is what makes cross-provider price comparison and automated settlement possible.
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/deployment
Deployment groups express requirements in shared resource units.
- x/market
Order/bid matching compares resource specifications from this module.
- x/settlement
Usage records quantify consumption in the same units they were leased in.
- x/benchmark
Benchmarks ground abstract units in measured hardware performance.
Key concepts
Terms that matter here
- Resource unit
- The canonical quantification of CPU, memory, storage, or accelerator capacity.
- Capacity
- A provider's leasable inventory, expressed in resource units for matching.
Keep exploring