Ore Compute whitepaper

Roles

• Miners run the ore worker on RTX GPUs and submit proofs.
• Coordinator issues jobs, checks bindings and records accepted work.
• Verifier checks each proof natively in an isolated process.
• Settlement worker credits balances every ten minutes, closes days and mints testnet ORE. A separate signer key signs claim vouchers; it holds no funds.
• Vault owner tops up the reward vault on mainnet, sets the minimum claim and daily limit, and can pause or withdraw. It is currently a single operator wallet, not a multisig.
• Admins review abuse flags, check tokens and publish season terms.

Job lifecycle

1. A paired worker requests a job with its scoped token.
2. The coordinator creates a random job that expires in five minutes, with a 76-byte challenge binding site, chain, season, day, worker, wallet and job ID.
3. The worker computes noisy INT7 matrix products on the GPU and searches for a transcript hash under the target.
4. The worker checks its result locally and submits a certificate-v3 proof.
5. The coordinator rebuilds the binding, calls the verifier, and credits the job once.

Verification

The verifier runs the unmodified py-pearl-mining 0.3.1 module from the pinned Pearl revision. It admits only dense rank-128 proofs with K = 2048 or 4096 and one opened tile, for known targets. It runs each proof in a child process with memory, CPU and file limits, and returns "not valid" on any error.

Season accounting

• 7 UTC days; 1,000,000 ORE per season.
• 950,000 ORE for mining (about 135,714.2857 per day, remainder on the last day); up to 50,000 ORE for referrals.
• Each day is split by difficulty-weighted accepted work, using exact integers and largest-remainder rounding.
• No work, no issuance. Unissued and unclaimed rewards go to the token's reserve.

Reward selection

Before each season after the first, an admin sets a budget, publishes three tokens that pass on-chain and market checks, and miners vote for 24 hours by signed message. Voting power is accepted ORE from finalized days when voting opens. Ties go to higher liquidity. The winner's address, pool, rate and funding plan are published before the season starts.

Settlement

1. Each closed day is finalized and minted to OreToken through MiningDistributor, which enforces caps.
2. Every ten minutes, the closed window's share of the day cap is split by accepted work and added to each wallet's balance.
3. At season close the referral bonus is added.
4. A miner's claim is a voucher for their cumulative earned total, signed by the signer key and valid for ten minutes. The vault pays the difference from what was already claimed, if it reaches the minimum claim and fits in the daily payout limit. The server never holds the owner key.
5. Every step is reconciled and safe to restart.

AI service

The Playground and API forward requests to a third-party model provider. Each request reserves its maximum cost, then charges the exact provider cost plus a margin. Prompts and responses are not stored on our servers. Credits are bought with USDG, or ETH priced with a Chainlink feed when one is configured, on Robinhood Chain Mainnet.

Trust limits

The contracts do not re-run the proof computation. You trust the operator to run the verifier and sign honest claim vouchers; testnet ORE mints and the fixed rate let anyone check totals after each day. The vault does not reserve tokens for unclaimed balances, and the owner can withdraw from it. An accepted proof does not attest a physical GPU. The contracts have not been audited.

Parameters