Topic: Will merged mining kill the pools? (Read 1186 times)
#5 won't work. Pools still have full control over what merged mining child blocks are attached to the work they send out and what the payout addresses are on those blocks. So long as they don't intentionally provide a way of requesting or sending in work that can be used to withhold payments we should be OK. (It's even entirely safe for a pool on a network that doesn't support merged mining, like Bitcoin, to allow you to add your own merged mining payloads to the work you request so you can mine solo on another blockchain.)
Can you explain to the uninitiated how does #5 work? I don't know a lot about merged mining, but in normal mining this is impossible since a pool's getwork gives all rewards to the pool.
But if this attack is possible and no other solution is found, pools will have to lobby that much harder for oblivious shares.
But if this attack is possible and no other solution is found, pools will have to lobby that much harder for oblivious shares.
1. miner getwork from pool
2. pool sends a difficult=1 work share to miner
3. miner works on the share
4. if the share doesn't solve the current block, miner sends the result to the pool, and get paid for the share from the pool
5. if the share solves the current block, miner sends the result to a solo mining server, get paid for the block
6. so a miner can get paid twice, and if everyone do this, a pool can never solve a block. lol
2. pool sends a difficult=1 work share to miner
3. miner works on the share
4. if the share doesn't solve the current block, miner sends the result to the pool, and get paid for the share from the pool
5. if the share solves the current block, miner sends the result to a solo mining server, get paid for the block
6. so a miner can get paid twice, and if everyone do this, a pool can never solve a block. lol
Jump to: