Pool operators kit
This section is for anyone running a Zecnero mining pool or writing pool software. It covers what differs from a Monero or Zcash pool.
What a pool needs
| Need | Detail |
|---|---|
| A synced node | zecnerod, see Run a node |
| Block templates | getblocktemplate from the node’s Zebra-compatible JSON-RPC. See Block template. |
| Proof of work | RandomX rx/zecnero. See Key schedule. |
| Share target | Your own vardiff target below the network target. |
| Founder output | Every coinbase must pay the founder stream until the first halving. |
| Coinbase maturity | 100 blocks before a coinbase can be spent. |
| Reorg handling | Nodes reject reorgs deeper than 20 blocks. |
| Test vectors | 17 RandomX-Zecnero vectors. See Test vectors. |
How a block flows
Checklist before going live
- Node synced and on the latest release.
- Templates include the founder output with the exact amount.
- RandomX seed hash switches at the right heights. Test across an epoch boundary.
- All 17 test vectors pass in your hashing code.
- Payouts wait at least 100 confirmations on the coinbase.
- Your stratum server handles the 75 second block time without stale-share spikes.
- You have a plan to upgrade within 72 hours of a release announcement.
Contact
Pool operators can reach the team at zecnero@zecnero.org or in Discord. Tell us your pool’s URL so we can include you in upgrade notices.
TODO
Confirm whether there is a dedicated pool operators channel or mailing list for upgrade notices.