Re: [bitcoin-dev] Segwit v2

Johnson Lau, > not change the commitment structure as suggested by another post Not sure if you realize my proposal is backwards compatible. We could also merge the two arrays, which would be harder to compress, but a more simple format. Below I gave an example of how this would be backwards

Re: [bitcoin-dev] Segwit v2

On Wed, Apr 26, 2017 at 4:01 PM, Luke Dashjr via bitcoin-dev < bitcoin-dev@lists.linuxfoundation.org> wrote: > There are things scriptSig can do that witness cannot today - specifically > add > additional conditions under the signature. We can always obsolete scriptSig > later, after segwit has

Re: [bitcoin-dev] Segwit v2

> On 27 Apr 2017, at 04:01, Luke Dashjr wrote: > > On Wednesday 26 April 2017 7:31:38 PM Johnson Lau wrote: >> I prefer not to do anything that requires pools software upgrade or wallet >> upgrade. So I prefer to keep the dummy marker, and not change the >> commitment structure

Re: [bitcoin-dev] Segwit v2

On Wednesday 26 April 2017 7:31:38 PM Johnson Lau wrote: > I prefer not to do anything that requires pools software upgrade or wallet > upgrade. So I prefer to keep the dummy marker, and not change the > commitment structure as suggested by another post. Fair enough, I guess. Although I think the

Re: [bitcoin-dev] Segwit v2

I prefer not to do anything that requires pools software upgrade or wallet upgrade. So I prefer to keep the dummy marker, and not change the commitment structure as suggested by another post. For your second suggestion, I think we should keep scriptSig empty as that should be obsoleted. If you

Re: [bitcoin-dev] Draft BIP: Segwit deployment with versionbits and guaranteed lock-in

See Segwit v2 thread. Maybe we can collaborate on combining these. On Wednesday 26 April 2017 6:15:26 PM shaolinfry via bitcoin-dev wrote: > This is a draft BIP proposal to redeploy segwit using BIP-8, from the day > after the current BIP9 segwit times out. > > This BIP could be deployed long

[bitcoin-dev] Draft BIP: Segwit deployment with versionbits and guaranteed lock-in

This is a draft BIP proposal to redeploy segwit using BIP-8, from the day after the current BIP9 segwit times out. This BIP could be deployed long before Nov 15th 2016, for example in July allowing wide deployment to begin soon. The timeout (and this useractivation) could be set to roughly a

Re: [bitcoin-dev] Segwit v2

Luke, I can't really advise on your proposed changes... but I have a couple new suggestions: === Future Proof Commitment Extension Methodology === 1. I'm not a fan of how ambiguous the direction is on handling future commitment extensions. See