Mining
How mining works
Jobs, proofs, verification and how accepted work becomes ORE.
Jobs
A worker asks the coordinator for a job. Each job is random and expires after five minutes. Its 76-byte challenge binds the site, chain, season, UTC day, worker, wallet and a random job ID.
Work and proof
The worker generates matrices, adds noise derived from the challenge, and multiplies them on the GPU. It hashes partial results and looks for a result under the job's target. When it finds one, it builds a proof that opens one tile of the computation, using Pearl's certificate-v3 format.
Because the noise depends on the challenge, a proof cannot be moved to another job or wallet.
Verification
The coordinator sends the stored challenge and the proof to the native verifier. The verifier runs in an isolated process with memory and CPU limits and fails closed: if anything goes wrong, the proof is not accepted. A database constraint makes sure each job is credited at most once.
The worker's own numbers, such as speed or uptime, are never trusted.
From accepted work to ORE
- Each accepted proof carries a difficulty weight.
- When a UTC day closes, that day's 135,714.2857 ORE is split across wallets by their weighted accepted work.
- A day with no accepted work issues no ORE.
ORE is minted on Robinhood Chain Testnet as a non-transferable record.
What a proof does not show
An accepted proof shows that valid work was done for a job. It does not attest which physical GPU did the work, and the RTX worker does not serve AI requests.