Reference
Network and proofs
The work protocol, verification checks and contracts in detail.
Work protocol
Protocol ore-plain-v1 uses Pearl's 76-byte certificate-v3 header: version, a 32-byte domain, a 32-byte commitment, a timestamp and the target bits.
- Domain: SHA-256 of the site origin, chain 46630, season, day and UTC day.
- Commitment: SHA-256 of the chain, Worker ID, wallet, season, day and the random job ID.
These are synthetic challenges for Ore Compute. They are not blocks of any blockchain.
Proof checks
- The job belongs to this worker and wallet and has not expired.
- The stored challenge still matches its binding.
- The native verifier accepts the dense rank-128 proof (K = 2048 or 4096, one 4×8 tile) for that exact challenge and target.
- The job and the proof hash are each credited once, enforced by database constraints.
The verifier is the unmodified py-pearl-mining 0.3.1 native module built from the pinned Pearl revision, run in a resource-limited child process.
Contracts
| Contract | Chain | Purpose |
|---|---|---|
| OreToken | Testnet 46630 | Non-transferable ORE record; only the distributor mints |
| MiningDistributor | Testnet 46630 | Daily batch mints with per-season and per-day caps |
| RewardVault | Mainnet 4663 | Holds reward tokens; signed-voucher claims at any time above the minimum, with a daily payout limit |
| CreditsPayment | Mainnet 4663 | ETH and USDG payments forwarded to the treasury |
Contract addresses are published here and on the Status page once they are deployed. The contracts have not been audited.