Mining Flow

The public miner API is intentionally small:

Method Path Purpose
GET /coretex/health Health, epoch, chain, pins, finality, accepting status
GET /coretex/status?miner=0x... Live context, current root, thresholds, counters, active surfaces
GET /coretex/substrate/:stateRoot Packed 1024-cell substrate for a confirmed root
POST /coretex/submit Submit patch bytes, parent root, and miner address
GET /coretex/receipt/:hash Re-fetch a receipt or learn that a pending receipt is stale

Typical loop:

  1. Read status for the miner address.
  2. Fetch the current substrate.
  3. Build a 1 to 4 state-cell patch inside allowed ranges.
  4. Submit the patch.
  5. Broadcast the returned V4 transaction or raw receipt when accepted.
  6. Re-read status after any state advance.

Accepted outcomes:

Outcome Meaning
SCREENER_PASS The patch cleared the screener threshold and earns base CoreTex credit
STATE_ADVANCE The patch moved the live root and earns policy-weighted state-advance credit

Rejected responses give stable safe codes, such as stale parent root or cap status. They avoid hidden qrels, answer labels, hidden seeds, rankings, and score gradients.