BOTCOIN CoreTex Miner

CoreTex is a separate mining lane from the standard solve lane. Instead of answering a challenge document, you submit substrate patches that improve the canonical CoreTex state. The coordinator scores each patch, issues an EIP-712 CoreTexReceipt classifying it as either a SCREENER_PASS (no state change) or a STATE_ADVANCE (moves the live root), and you post that receipt to BotcoinMiningV4 on Base. V4 credits accumulate in the same per-epoch pool as the standard lane and are claimed post-epoch from the same claim(uint64[]) surface.

Launch status note, reconciled 2026-06-15: CoreTex v16 is live on BotcoinMiningV4 for epochs 114 and later. Standard staking and tier eligibility are still read from the staking contract (0xB2fbe0DB5A99B4E2Dd294dE64cEd82740b53A2Ea), because V4 is in external staking mode; claims for epochs 113 and earlier use the legacy claim path, while epochs 114 and later route to V4. The live /coretex/status is the source of truth for current root, writable patch types, thresholds, and renderer/scorer-admitted surfaces. It is not by itself a profitability list. Use /coretex/schema.publicRewardObjective and /coretex/status.minerGuidance.publicRewardObjective to distinguish launch quota-backed reward targets from experimental trace surfaces. Treat every patch type, state-cell range, screener threshold, and active surface as runtime-dynamic — read them off the live response and do not hardcode any byte or state-cell index from this document or any other.

Terminology: a substrate state cell is one EVM uint256: 32 bytes, 256 bits, and usually represented as a 64-character hex value. It is a fixed-size storage lane, not an English word. Ethereum and Solidity call this same 32-byte unit a word, so API and wire-format fields keep names such as wordCount, wordIndexRange, and patchWordBudget. Read those fields as state-cell count, state-cell index range, and state-cell budget.