Module reference · Marketplace & workloads
x/marketplace — Marketplace
Marketplace coordination and offering surfaces layered over the core exchange.
What it does
Inside x/marketplace
Where x/market implements the raw order–bid–lease state machine, the marketplace module carries the coordination surfaces around it: how offerings are presented, how marketplace-level rules are applied, and how the exchange is exposed to client interfaces as a coherent product rather than a bag of primitives.
It gives the protocol a place to evolve marketplace behavior — listing rules, offering metadata, cross-module orchestration — without overloading the core matching engine, keeping the state machine in x/market small and verifiable.
Why it exists
The design rationale
Separating the matching engine from marketplace presentation is a deliberate design split: the core exchange must stay minimal and stable, while the marketplace surface can grow with the network. The two-module split keeps consensus-critical logic isolated from product-level iteration.
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
Builds directly on the order, bid, and lease primitives.
- x/provider
Surfaces provider offerings and attributes to tenants.
- x/resources
Uses shared resource definitions to describe offerings consistently.
- x/review
Reputation signals feed offer presentation and tenant choice.
Key concepts
Terms that matter here
- Offering
- A provider-facing presentation of leasable capacity, described with shared resource units and attributes.
- Approved client
- A client interface permitted to interact with identity-sensitive marketplace flows, governed via x/config.
Keep exploring