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 improvem
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.
_
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 size
Some discussion today led me to believe that a post segwit hard fork could
include:
1MB old tx non-witness segment
XMB new segwit non-witness segment
XMB witness segment
By partitioning off old transactions, it allows users of older, more
expensive validation transactions to continue using them,
