We changed our privacy policy. Read more.

The work given by a pool includes the coinbase transaction which defines the payment as going to the pool, and is unique to that. If the client modifies the payout address, the proof of work they have done is invalidated. They can not steal money from the pool by doing this.


They don't have any special hardware, as pools don't meaningfully produce merkle roots in any volume. Since the original answer in 2013 which pertained to GetWork, mining has moved entirely to using the Stratum protocol which has the mining client generate their own merkle roots for proof of work, based on a template that is provided by the pool and is the ...


The post I linked suggests that it's offloaded, but why - since wouldn't this be slower? Is the next Merkle root precomputed while hashing of the previous header is being performed by the ASIC? It is not noticeably slower because merkle root computations make up a negligible amount of hashes computed. It is likely to implementing faster merkle root ...


Why can't we change default minimum fee rate to something below 1 sat/vByte? I think I'm reading in sipa's answer the number is simply set arbitrarily low enough so that spam is not a problem. If that's the reason, I suppose the answer to your question is "we actually can change it". We could set it to 0.2 sat/vByte like you were writing about, ...

Only top voted, non community-wiki answers of a minimum length are eligible