Compute Marketplace

Buyers pay in it, providers earn it, and it is the single source of truth for balances and supply. One currency end to end, not a separate notion of credits.

• Symbol MATRIX, 9 native decimals on the Matrix L1
• Supply capped at 1,000,000,000 whole MATRIX; balances live on the consensus ledger
• A genesis allocation plus a genesis-funded reward pool back earnings as capped, supply-tracked issuance (no unlimited minting)
• All settlement is applied deterministically once a consensus block commits

• Lock to mint — native MATRIX is locked on the L1, and a threshold of validator secp256k1 attestations authorizes minting the matching wMATRIX
• Burn to unlock - burning wMATRIX emits an on-chain Burned event. A watcher inside the node polls Ethereum for those events past a confirmation depth, keeps a persisted scan cursor across restarts, and releases the escrowed native MATRIX exactly once per event (keyed by transaction hash and log index).
• Native has 9 decimals and wMATRIX has 18, so one native base unit equals 1e9 wrapped base units and the 1,000,000,000 MATRIX cap maps to the same money on both sides
• Runs against local and test networks only; it is not deployed to any public Ethereum network

• ed25519 validator set, round-robin leader, no proof-of-work
• A quorum is more than two thirds of the set, in both voting phases
• Round timeouts rotate the leader, and the next leader must re-propose the block that last reached a polka, carrying the polka as proof
• Committed blocks are SHA-256 hash-linked into one chain every node shares
• A node that missed a block fetches it from a peer with the quorum that committed it

Consensus is the authoritative, globally agreed ledger for marketplace settlement. Both the compute marketplace and the LLM inference marketplace settle buyer to provider through consensus in native MATRIX by default. The earlier per-node pairwise settlement and the direct token-chain transfer remain as separate, non-default primitives for point-to-point transfers, but the marketplace flows no longer use them.

Inference is a pluggable backend, so a provider can contribute compute in two ways:

• Local runner — serve a model from your own hardware through an Ollama-style local HTTP API. A GPU-free echo backend runs the whole flow for testing.
• Provider-API proxy — proxy requests through an OpenAI-compatible API. The key is read from an environment variable and never hardcoded or committed.

Jobs are submitted over the matrix.inference.v1 InferenceService, capacity is reserved with an up-front affordability check on the reserved price, the backend runs the request, and the job settles buyer-to-provider in native MATRIX through the consensus ledger. The charge is scaled by the provider's price per unit and capped at the reserved amount, and the job is reported COMPLETED only once that settlement commits and applies on the ledger.