Repository navigation
QDAY v0.7.0: Mining pools
If you want to run a QDAY mining pool, start here.
This release gives external pool software an official transaction-aware block template API. Stop building empty blocks by hand.
What changed
- Added authenticated
POST /api/miner/getblocktemplate. - Added authenticated
POST /api/miner/submitblock. - Templates include the miner payout, QDAY coinbase marker, mempool transactions, fees and block commitment.
- Long polling returns fresh work when the chain or mempool changes, or after 30 seconds.
- Locally submitted sends, burns and PQ Day proofs now survive node restarts and rebroadcast for up to 48 hours.
- Added the reproducible NUMS canary derivation tool and verification document.
Running a pool
- Replace your QDAY node with
v0.7.0. Existing wallets and chain data remain compatible. No resync is required. - Create or import the pool payout wallet and unlock it.
- Keep the API private on
127.0.0.1:19770. - Read the bearer token from
api.tokenin the QDAY data directory. - Request work:
POST /api/miner/getblocktemplate
Authorization: Bearer <api.token>
Content-Type: application/json
{"longpollid":""}- Send the returned
headerandtargetto your workers. The header is the complete 80-byte BLAKE2b-256 work item. - Repeat the request with the returned
longpollid. Replace worker jobs whenever the request returns. - When a worker finds a valid nonce, reconstruct the complete QDAY block and submit its Sia binary encoding:
POST /api/miner/submitblock
Authorization: Bearer <api.token>
Content-Type: application/json
{"params":["<hex-encoded-complete-block>"]}QDAY does not ship a Stratum server. Your pool controller translates Stratum or whatever ritual your workers speak into these two local endpoints.
Full pool integration guide:
https://github.com/petoshi/qday/blob/v0.7.0/docs/integrations.md
Same mainnet. Same genesis. Same consensus. Ordinary wallets do not need this release to remain on the network.
Mining pools do.