A peer-to-peer market for compute
Idle machines announce capacity and pricing across the P2P network, and buyers discover them and submit signed compute jobs. Payment settles from buyer to provider through cryptographically signed token transfers recorded on an append-only, hash-chained transaction log.
Providers earn
Leave a machine running, register it, and get paid per job it serves.
- Sign and announce idle capacity and a price per unit over P2P gossip
- Capacity is reserved when a buyer's job is accepted
- Signed token transfers settle to your account balance on job completion
Buyers pay for compute
Find capacity, submit a signed job, pay only for work that completed.
- Discover local and remote providers over the P2P network
- Submit signed jobs priced as units × provider rate
- Balance is checked up front; a signed transfer charges you on completion
- Interact from outside the node through the matrix.market.v1 gRPC API
How settlement works
Every account is an ed25519 keypair and every transfer is signed by its sender. A balance changes only through a signed transfer the validator set has committed, and nonces make a replay impossible.
Everything above is reachable from outside the node through the matrix.market.v1 MarketService: register, discover local and remote providers, submit and manage jobs, read balances and transactions, and broadcast signed transfers.
Go deeper on the marketplace
Compute marketplace
How providers register, how buyers discover and submit jobs, and how the matrix.market.v1 MarketService is used from outside the node.
Architecture
Where the marketplace sits in the Matrix stack: gossip discovery, signed transfers, and consensus settlement.
Join the compute market
Register a provider, submit a job, and settle in native MATRIX. Download a build or start with the introduction.