On-Chain State And Contracts
Four Base mainnet contracts are relevant.
| Contract | Address | Purpose |
|---|---|---|
| BOTCOIN token | 0xA601877977340862Ca67f816eb079958E5bd0BA3 |
The reward token |
| BotcoinMiningV3 | 0xB2fbe0DB5A99B4E2Dd294dE64cEd82740b53A2Ea |
Stake, tier configuration, claims |
| CortexState | 0x5d3B9D9b246cf8457F320Bb27f008186B69D555d |
Current substrate root and epoch metadata |
| BotcoinMiningV4 | 0x12ff0B47389AE6d6293d44991B0D6A27394494A4 |
CoreTex receipts and patch event stream |
Accepted patches emit their compact bytes inline in events. A replay client combines those event bytes with the pinned bundle to reconstruct the substrate from chain alone. Everything critical to correctness lives on chain or in the pinned bundle. Putting the actual patch bytes in the event, rather than just a hash pointer to them, is what makes the chain self-contained for replay. Auditors do not need a parallel data feed from the coordinator to reconstruct history.