It's not the pool operator's business what software the miner is running to select transactions for his block, so long as the miner follows the template and doesn't generate invalid blocks. We already discussed invalid blocks, and checking the template requires parsing the coinbase transaction and verifying the merkleroot. The most expensive operations are the hashes in the merkleroot verification, but you have to do that in stratum too because of the extranonce, right?
On 06/19/2014 01:55 PM, slush wrote: > Miner issues are just one thing what came to my mind. What about > validating transactions? How the pool can be sure that miner is running > up to date bitcoind which do full validation of transactions? Not > talking that if every miner takes his own set of transaction, pool need > to calculate merkle root for every submit, to check its correctness. ------------------------------------------------------------------------------ HPCC Systems Open Source Big Data Platform from LexisNexis Risk Solutions Find What Matters Most in Your Big Data with HPCC Systems Open Source. Fast. Scalable. Simple. Ideal for Dirty Data. Leverages Graph Analysis for Fast Processing & Easy Data Exploration http://p.sf.net/sfu/hpccsystems _______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
