On-Chain State And Contracts
CoreTex uses on-chain roots, events, and snapshots rather than storing the full corpus on chain.
On-Chain Data
| Data | Purpose |
|---|---|
liveStateRoot |
Current state root during the epoch |
CoreTexStateAdvanced |
Records an accepted state advance |
CoreTexPatchAccepted |
Carries compact patch bytes for replay |
CoreTexEpochFinalized |
Commits final epoch roots |
CoreTexStateSnapshot |
Periodic full 32 KB state snapshot |
coreTexVersionHash |
Pins the exact CoreTex logic |
experienceCorpusRoot |
Pins the evaluated corpus |
Data Availability
Accepted patches include the compact patch bytes. Snapshots every 100 epochs carry the full 1024-word state. A fresh validator can reconstruct from the latest snapshot rather than replaying from genesis forever.
This 100-epoch snapshot cadence is not an update cadence. CoreTex still uses 24-hour BOTCOIN epochs, and verified improvements can advance the live state many times inside a single epoch. The 100-epoch snapshot is only a sync and audit convenience.