Re: [bitcoin-dev] Introducing a POW through a soft-fork

2017-11-11 Thread Eric Voskuil via bitcoin-dev
> On Nov 6, 2017, at 20:38, Devrandom wrote: > > A hard-fork is a situation where non-upgraded nodes reject a block mined and > relayed by upgraded nodes. As Peter pointed out, that is the case here. > This creates a fork that cannot heal regardless of what follows.

Re: [bitcoin-dev] Introducing a POW through a soft-fork

2017-11-06 Thread Devrandom via bitcoin-dev
A hard-fork is a situation where non-upgraded nodes reject a block mined and relayed by upgraded nodes. This creates a fork that cannot heal regardless of what follows. This proposal is not a hard-fork, because the non-upgraded node *will heal* if the attack has less than 1/2 of the original-POW

Re: [bitcoin-dev] Introducing a POW through a soft-fork

2017-11-06 Thread Eric Voskuil via bitcoin-dev
If a block that would be discarded under previous rules becomes accepted after a rule addition, there is no reason to not simply call the new rule a hard fork. IOW it's perfectly rational to consider a weaker block as "invalid" relative to the strong chain. As such I don't see any reason to

Re: [bitcoin-dev] Introducing a POW through a soft-fork

2017-11-06 Thread Devrandom via bitcoin-dev
> > Note how you're basically proposing for the block interval to be decreased, >> which has security implications due to increased orphan rates. >> > > Note that the total transaction rate and block size don't materially > change, so I don't > see why the orphan rate will change. Normal blocks

Re: [bitcoin-dev] Introducing a POW through a soft-fork

2017-11-02 Thread Devrandom via bitcoin-dev
I am also concerned. However, this proposal allows two POWs to coexist and allows for gradual transitions. This is hopefully a less disruptive approach since it allows cooperative miners to migrate over time. And of course, as a soft-fork it keeps backwards compatibility with existing software.

Re: [bitcoin-dev] Introducing a POW through a soft-fork

2017-11-02 Thread Tao Effect via bitcoin-dev
Just going to throw in my support for a POW change, not any particular implementation, but the idea. Bitcoin is technically owned by China now. That's not acceptable. - Greg -- Please do not email me anything that you are not comfortable also sharing with the NSA. > On Oct 31, 2017, at 10:48

[bitcoin-dev] Introducing a POW through a soft-fork

2017-11-02 Thread Devrandom via bitcoin-dev
Hi all, Feedback is welcome on the draft below. In particular, I want to see if there is interest in further development of the idea and also interested in any attack vectors or undesirable dynamics. (Formatted version available here: