MerkleMaker: Always prefer the highest block from any source
authorLuke Dashjr <luke-jr+git@utopios.org>
Thu, 21 Feb 2013 06:07:42 +0000 (06:07 +0000)
committerLuke Dashjr <luke-jr+git@utopios.org>
Thu, 21 Feb 2013 06:07:44 +0000 (06:07 +0000)
commit7a8c512b5f693637a269c2cabe8da1e6742744d0
tree74d36a216595e8eeab97569ae82882aa724df84a
parentde79b85a3f040c109f81a91178968886e9d22711
MerkleMaker: Always prefer the highest block from any source

This was already necessitated by _ProcessGBT calling updateBlock when it saw a new height (to rush out blank jobs)
Without it, race conditions would result in Eloipool reversing this decision and going back to the old block
This also meant it invalidated and wasted all the longpoll work
merklemaker.py