Mining Flow

The public API is enough to mine; the full client is optional. Keeping the API path viable matters because the design promise is wide participation, and requiring every miner to set up the local verifier stack would push out anyone without the resources to run it.

A typical flow: GET /coretex/challenge to pull the current work packet (parent state root, substrate, and the coreVersionHash that pins the patch schema), build a 1-4 word patch, then POST /coretex/submit with the patch. The coordinator runs the scoring against the per-patch hidden pack derived from a future blockhash. If the patch qualifies, the response is {status: "accepted", receipt, patchHash, evalReportHash}; otherwise {status: "rejected", ...}. On acceptance the miner submits the signed receipt to BotcoinMiningV4. The chain emits the patch bytes, the credit award, and the state advance as events.