Re: [bitcoin-dev] Blockchain verification flag (BIP draft)

2015-12-05 Thread Gregory Maxwell via bitcoin-dev
On Sun, Dec 6, 2015 at 2:47 AM, James Hilliard via bitcoin-dev wrote: > I think something that anyone who isn't validating should be aware of is > that cgminer(which powers the vast majority of the current mining network) > doesn't allow for a pool to revert to mining on the previous block due to

Re: [bitcoin-dev] Blockchain verification flag (BIP draft)

2015-12-05 Thread James Hilliard via bitcoin-dev
I think something that anyone who isn't validating should be aware of is that cgminer(which powers the vast majority of the current mining network) doesn't allow for a pool to revert to mining on the previous block due to the way chain tracking is implemented. https://github.com/ckolivas/cgminer/b

Re: [bitcoin-dev] Blockchain verification flag (BIP draft)

2015-12-05 Thread Gregory Maxwell via bitcoin-dev
On Fri, Dec 4, 2015 at 10:43 PM, Rusty Russell wrote: >> I agree with Jannes Faber, behavior with respect to SPV clients should be >> to only tell them about fully validated headers. > > A delicate balance. If we penalize these blocks too much, it's > disincentive to set the bit. Fortunately it'

Re: [bitcoin-dev] Blockchain verification flag (BIP draft)

2015-12-05 Thread Rusty Russell via bitcoin-dev
Gavin Andresen via bitcoin-dev writes: > Overall, good idea. > > Is there a write-up somewhere describing in detail the 'accidental selfish > mining' problem that this mitigates? I think a link in the BIP to a fuller > description of the problem and how validation-skipping makes it go away > would