Verification And Replay

CoreTex is public-verifiable. A verifier needs:

• Base RPC access.
• The deployed contract addresses.
• The active bundle manifest.
• The corpus root and relevant corpus delta artifacts.
• Parent state snapshots or enough prior patch logs to reconstruct state.
• The revealed epoch secret after epoch close.
• Base RPC access to fetch the target blockhash recorded in each receipt.
• The signed patch-received notice or equivalent public submission log, when available.

Replay checks:

1. The bundle hash matches the epoch coreVersionHash.
2. The corpus root matches the bundle or epoch metadata.
3. The receipt's target blockhash matches Base chain data.
4. Gate and confirm seeds re-derive from the revealed epoch secret, blockhash, patch hash, miner, parent root, corpus root, and bundle hash.
5. Gate and confirm query packs re-derive from those seeds.
6. Accepted patch bytes apply cleanly to the parent root.
7. The recomputed state root matches CortexStateAdvanced.
8. Evaluation reports match the pinned scorer within replayTolerancePpm.

The live coordinator is not the only verifier. The calibration host can run heavier model checks, the coordinator can run bounded-throughput evaluation, and independent users can run the client more slowly on their own machines.