COMPUTE PROVIDERS

Kronex creates an open marketplace for computational resources.

Applications, companies, developers and autonomous agents will be able to request computing capacity from independent providers.

planned This page describes planned functionality.

01 · WHAT THIS PROVIDER DOES

What this provider does

Provides CPU, GPU or specialized computation.

Providers monetize unused or dedicated hardware. Buyers access compute without relying on a single centralized infrastructure operator.

ORDER SELECTED
Fig. 01 — provider selection

An order fans out to the providers able to serve it; one is selected on the buyer's requirements, not on price alone.

02 · WHAT ORDERS IT RECEIVES

What orders it receives

Compute markets may include

  • AI inference
  • GPU computation
  • AI agent workloads
  • model execution
  • rendering
  • ZK proving
  • batch processing
  • Proof-of-Work computation
  • specialized computing hardware

03 · REQUIREMENTSSpecification pending

Requirements

Indicative until specified. These are the categories a compute provider is expected to satisfy, not the values it must meet.

Hardware
The class of hardware offered and how it is described to the market.
Availability
The uptime a provider commits to for the duration of an order.
Region
Where the hardware is, for orders that constrain it.
Collateral
What is staked against the delivery a provider accepts.

Requirements will be published with the provider framework.

04 · HOW IT IS PAID

How it is paid

Compute fees are one of the protocol's fee sources. A provider is paid for the workload it completes, settled against the verified result.

05 · HOW IT IS MEASURED

How it is measured

  • uptime
  • successful executions
  • response time
  • delivery accuracy
  • collateral
  • execution quality

Applications can automatically choose providers according to their own requirements.

06 · RISKS AND OBLIGATIONSSpecification pending

Risks and obligations

A provider commits hardware for the duration of an order and collateral against the delivery it accepts. Settlement follows the verified result, and a provider that fails to deliver is exposed to economic penalties where appropriate.

The penalty mechanism is not designed.

  • hardware committed for the order
  • collateral at stake
  • penalties where appropriate

07 · ROADMAP DEPENDENCY

Roadmap dependency

Phase 4

Compute & AI Marketplanned

create an open marketplace for AI and computational infrastructure

  • GPU providers
  • compute orders
  • workload routing
  • AI inference market
  • execution receipts
  • provider benchmarking
  • compute APIs

Full roadmap →