Validator And Auditor Sync

A CoreTex validator is synced when it can replay chain events through the latest finalized epoch and produce the same state root as the contract.

The local sync state should track:

{
  "synced": true,
  "baseBlockLag": 2,
  "latestFinalizedEpoch": 812,
  "latestVerifiedEpoch": 812,
  "latestOnchainStateRoot": "0x...",
  "latestLocalStateRoot": "0x...",
  "matchesOnChain": true,
  "coreTexVersionHash": "0xe1a957...",
  "genesisStateRoot": "0x7e704f...",
  "lastSnapshotEpoch": 800,
  "auditWindowOpen": false
}

The key command is:

node packages/coretex/dist/cli.js verify-epoch <EPOCH> --rpc $BASE_RPC_URL

A healthy validator should show:

  • Base RPC near chain head
  • coreTexVersionHash equal to the published CoreTex V0 hash
  • genesisStateRoot equal to the frozen genesis root
  • Latest local root equal to the latest on-chain finalized root
  • Snapshot replay equal to full replay
  • No unresolved divergence inside the audit window

Eventually, validator operation can be rewarded, but the first production requirement is public reproducibility. Anyone should be able to prove whether the CoreTex root is correct.