Architecture

The CoreTex system consists of four primary components:

Botcoin CoreTex

Botcoin CoreTex is the deterministic CoreTex verifier. It is the small local program that:

• Packs and unpacks the 1024-word state
• Decodes typed memory slots
• Decodes and validates compact patches
• Applies 1-4 word state updates
• Maintains the state Merkle root
• Scores candidate states against CoreTexBench V0
• Replays finalized epochs from chain events

Botcoin CoreTex is the equivalent of the validator logic. It does not need a funded wallet and does not need coordinator trust to audit finalized roots.

CoreTex Server

The CoreTex server is the HTTP process mounted under /v1/coretex/*. It:

• Serves CoreTex challenges
• Enforces one outstanding challenge across the standard and CoreTex lanes
• Runs the real CoreTexBench evaluator
• Rejects no-improvement patches
• Requests receipt signatures through the existing coordinator internals
• Keeps local queue/state data in SQLite

Production mode requires real evaluation. Stub evaluation is fail-closed unless explicitly enabled for local development.

CoreTexRegistry

CoreTexRegistry is the on-chain state-root registry. It records:

• State advances during an epoch
• Finalized epoch roots
• Patch-set roots
• coreTexVersionHash
• Experience corpus root
• Benchmark commitment
• Periodic full-state snapshots
• Audit-window revert state

Validators And Auditors

Validators are independent Botcoin CoreTex processes that watch Base logs, reconstruct CoreTex state, and confirm that local replay matches the on-chain root. The coordinator should always run one, but anyone can run one.