Quote from: J35st3r on June 10, 2013, 12:09:56 PM

Quote from: os2sam on June 10, 2013, 11:59:29 AM

Right now everyone is trying to find a hash to solve Bitcoin Block 240,749. Nobody is trying to solve 240,748 nor 240,750, yet.

But, Skrat may well be referring you what you describe too?

Yeah, agreed. It was just a semantics niggle on my part. But in the case of network-partition (or if a block is solved simultaneously, to within net propagation time), there may well be pools working on two different version of block 240, 749. As I understand it, this issue is not resolved until the next block is solved, then at that point the longest chain is adopted globally, and the other block 240, 749 becomes orphaned, and that pool does not get paid.

I may be wrong though, just a newbie here, so correct me if I misunderstood. I haven't actually read Satoshi's paper yet, its on my to-do list

Sounds like your more knowledgeable than I am on the subject.

Each pool/bitcoind may include different transactions in their block so in that sense they are different blocks because they will have different content.

I've seen allot newbies confuse pool rounds and network blocks and I thought maybe he was doing something like that. But if not Skrat may want to look into using slush's stratum proxy to point multiple workers at the same pool.
Thanks,
Sam