Re: [bitcoin-dev] Quadratic hashing solution for a post-segwit hard fork

2017-03-17 Thread Jorge Timón via bitcoin-dev
Segwit allows old -> old, old -> new, new -> old and of course new -> new txs. On 17 Mar 2017 1:47 a.m., "Erik Aronesty via bitcoin-dev" < bitcoin-dev@lists.linuxfoundation.org> wrote: Yeah, it does make things harder, and it's easy enough to soft fork to handle arbitrary opt-in protocol

Re: [bitcoin-dev] Quadratic hashing solution for a post-segwit hard fork

2017-03-16 Thread Erik Aronesty via bitcoin-dev
Yeah, it does make things harder, and it's easy enough to soft fork to handle arbitrary opt-in protocol improvements, new much larger block sizes, whatever you want. Even OK to migrate to a new system by not allowing old->old or new->old transactions.

Re: [bitcoin-dev] Quadratic hashing solution for a post-segwit hard fork

2017-03-16 Thread Alphonse Pace via bitcoin-dev
This unnecessarily complicates transaction selection for miners by introducing a second (and possibly third if I understand your proposal correctly) dimension to try to optimize. See: https://en.wikipedia.org/wiki/Bin_packing_problem Segwit already solves this exact issue by replacing block