Receipts, Credits, And State Advances

Standard and CoreTex work share one per-rig receipt chain. Immediately before signing, the coordinator rechecks the epoch, rig eligibility, operator authorization, solve index, previous receipt hash, CoreTex parent, epoch context, and artifact availability. A changed CoreTex parent requires rebase. A standard receipt moving only the rig chain head can be rebound before signing after the other conditions are checked again.

The broadcast receipt EIP-712 domain is:

name:    BotcoinMiningRigs
version: 2
chainId: 8453

The verifying contract and exact RigCoreTexReceipt type come from the live schema and production deployment artifact. Candidate intake authorization uses a different EIP-712 domain and primary type: /coretex/v5/schema.candidatePackage.submissionAuthorization.eip712. Do not use the receipt domain to sign /coretex/v5/candidates.

An accepted state transition uses a compact descriptor containing a format version, a content address for the complete transition artifact, the parent state root, and the new state root. Its generalized format supports arbitrary M1-M6 release changes through the addressed artifact. The chain commits and orders the transition; validators fetch the complete artifact and reproduce it off chain.

The coordinator signs the receipt. The authorized rig operator broadcasts it to the mining contract. On success:

  1. the shared per-rig solve index and receipt hash advance;
  2. the contract computes credits from the rig's applicable tier snapshot and accepted work units;
  3. the verifier records the CoreTex result; and
  4. the registry advances liveStateRoot from the exact parent to the accepted new root.

Credit eligibility and claims follow the mining-rig contracts. The coordinator API reports current and snapshotted credit information, but the contract is the authority.

The current deployed reward policy pays accepted CoreTex quality and efficiency transitions through the same on-chain outcome/difficulty path. Admission gain ppm is carried for validation and audit; it is not a linear reward scalar. There is no CoreTex accepted-advance cap per epoch. Queue and per-operator occupancy controls protect evaluator capacity; they are not law, credit, or reward caps.

Consequently, a quality transition that spends capacity and a later efficiency transition that reclaims it can each earn the same current outcome. The fixed caps preserve resource safety; this flat-payment behavior is an economic property, not magnitude-sensitive pricing.