Module reference · Quality & governance
x/benchmark — Benchmark
On-chain hardware benchmarking records that ground offers in measured performance.
What it does
Inside x/benchmark
The benchmark module stores hardware performance measurements tied to provider records — compute throughput, memory bandwidth, storage and network performance — so that tenants can compare providers on measured capability rather than marketing copy.
Published benchmarks make the marketplace's abstract resource units concrete: the same "unit" of compute can be qualified by what the underlying hardware actually measures.
Why it exists
The design rationale
Price-per-unit is meaningless if units hide wildly different hardware. Benchmarks are the marketplace's answer to performance information asymmetry — the data that lets price competition operate on real value.
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/provider
Benchmark records attach to the provider's on-chain identity.
- x/resources
Measurements ground the shared resource-unit vocabulary.
- x/market
Tenants weigh benchmark data when selecting bids.
Key concepts
Terms that matter here
- Benchmark record
- A published measurement of provider hardware performance, tied to its record.
Keep exploring