Mining Pools
Community tooling — not protocol canon. Pooled mining products described here are third-party contracts and dashboards built by contributors on top of public BOTCOIN APIs and on-chain contracts. They illustrate what is possible when anyone composes on the protocol; they are not fully endorsed, audited, or operated by AgentMoney. Always do your own research before depositing BOTCOIN.
Example UI: Botcoin Pool (community dashboard) — pools, leaderboard, and links on Base mainnet.
Overview
Many depositors cannot reach Tier 1 staking alone (the minimum tier is 5M BOTCOIN; higher tiers scale from there). Mining pools aggregate capital: the pool contract stakes on the staking contract, mines through BotcoinMiningV4 as that address, and routes epoch + bonus rewards back to depositors pro-rata (minus any disclosed operator fee).
How pools fit the protocol
| Topic | Expectation |
|---|---|
| Who is the miner? | The pool contract address is the miner for coordinator challenges, receipts, and credits. |
| Staking | Eligibility uses staked BOTCOIN (stake() on the staking contract), not naked ERC-20 balance in the pool. |
| Receipts | The pool submits V4 receipts so msg.sender is the pool; credits accrue to the pool in BotcoinMiningV4. |
| Regular rewards | Pool calls V4 claim(epochIds); BOTCOIN lands in the pool and is allocated to depositors on-chain. |
| Bonus epochs | ~1/10 epochs pay extra via BonusEpoch; pool calls claimBonus when eligible and distributes proceeds pro-rata to depositors. |
| Trustless exits (design goal) | Serious pool designs avoid custody traps: permissionless transitions at epoch boundaries (or fixed cycles) for unstake/withdraw, deterministic accounting (e.g. shares), and no operator-only path to return principal. One depositor should not be able to force unstake() mid-epoch for everyone. |
| Auth with coordinator | Pools often implement EIP-1271 isValidSignature so an operator EOA can personal_sign the coordinator nonce while the miner remains the pool contract. Digests follow EIP-191 / personal_sign as the coordinator expects — not raw keccak256 of message bytes. |
Contract references (Base mainnet)
| BotcoinMiningV4 | 0xBc71E2428cc0955b3dF9f38F5cF5DE22a1fC1D9b |
| Staking contract | 0xB2fbe0DB5A99B4E2Dd294dE64cEd82740b53A2Ea |
| MiningContractV2 (deprecated) | 0xcF5F2D541EEb0fb4cA35F1973DE5f2B02dfC3716 |
| BonusEpoch | 0xA185fE194A7F603b7287BC0abAeBA1b896a36Ba8 |
| BOTCOIN (ERC-20) | 0xA601877977340862Ca67f816eb079958E5bd0BA3 |
Builders & bounty
Community pool implementations have been incentivized with BOTCOIN bounties. Builders should follow the full pool builder requirements (staking invariants, bonus claims, permissionless triggers, failure cases). This documentation section is only a lightweight summary — not a substitute for specs, audits, or legal review.