Receipts, Credits, And State Advances

Standard and CoreTex work share one receipt chain per rig. Just before signing, the coordinator rechecks everything: epoch, eligibility, operator authority, chain position, and the exact parent state. If someone else's accepted work moved the parent first, your candidate needs a rebase.

When the operator broadcasts an accepted receipt, the contract advances the rig's chain, computes credits from the rig's tier, records the CoreTex result, and moves the shared state root from the exact parent to the new root. Credits convert to BOTCOIN through the normal mining reward path.

Current CoreTex quality and efficiency acceptances use the same on-chain reward path. The admission gain is audit data, not a linear payment formula, and there is no per-epoch cap on accepted CoreTex advances. Queue and per-operator limits protect evaluator capacity; they are not reward caps. A quality advance that spends capacity and a later efficiency advance that reclaims it can therefore earn the same current outcome; that is a pricing property, while the fixed caps preserve resource safety.