Re: [bitcoin-dev] SIGHASH_ANYPREVOUT proposal

2019-05-27 Thread Rusty Russell via bitcoin-dev
Anthony Towns writes: > On Wed, May 22, 2019 at 12:17:31PM +0930, Rusty Russell wrote: >>I prefer to >>change the bip introduction to expliclty shout "THESE SIGNATURE >>HASHES ARE UNSAFE FOR NORMAL WALLET USAGE.", and maybe rename it >>SIGHASH_UNSAFE_ANYPREVOUT. > >> 4. "Rebinding

Re: [bitcoin-dev] SIGHASH_ANYPREVOUT proposal

2019-05-23 Thread Anthony Towns via bitcoin-dev
On Wed, May 22, 2019 at 12:17:31PM +0930, Rusty Russell wrote: >I prefer to >change the bip introduction to expliclty shout "THESE SIGNATURE >HASHES ARE UNSAFE FOR NORMAL WALLET USAGE.", and maybe rename it >SIGHASH_UNSAFE_ANYPREVOUT. > 4. "Rebinding is a new power in bitcoin, and

Re: [bitcoin-dev] SIGHASH_ANYPREVOUT proposal

2019-05-22 Thread Rusty Russell via bitcoin-dev
Anthony Towns via bitcoin-dev writes: > Hi everybody! > > Here is a followup BIP draft that enables SIGHASH_ANYPREVOUT and > SIGHASH_ANYPREVOUTANYSCRIPT on top of taproot/tapscript. (This is NOINPUT, > despite the name change) I really like this proposal, and am impressed with how cleanly it

[bitcoin-dev] SIGHASH_ANYPREVOUT proposal

2019-05-11 Thread Anthony Towns via bitcoin-dev
Hi everybody! Here is a followup BIP draft that enables SIGHASH_ANYPREVOUT and SIGHASH_ANYPREVOUTANYSCRIPT on top of taproot/tapscript. (This is NOINPUT, despite the name change) I don't think we are (or should be) as confident that ANYPREVOUT is ready for implementation and deployment as we are