[Bitcoin-development] Proposal to change payment protocol signing

Ryan X. Charles ryan at bitpay.com
Mon Apr 28 20:53:41 UTC 2014

Agreed with Mike. It doesn't really matter what the signature field is
set to. Changing the standard now is too hard with too little benefit.

On 4/28/14, 12:14 PM, Mike Hearn wrote:
> Who cares what it is? Setting to an empty byte array is fine, IMO. The
> payment protocol is already rolling out. It's implemented in several
> wallets, BitPay implements it, Coinbase is implementing it, etc.
> -100000 for changing such a basic thing at this point. It'd cause chaos
> for the early adopters, punishing them instead of rewarding them. It'd
> seriously hurt adoption of the payment protocol when it's at its most
> vulnerable. We should mark BIP 70 as accepted and be done with it. 
> ------------------------------------------------------------------------------
> "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE
> Instantly run your Selenium tests across 300+ browser/OS combos.  Get 
> unparalleled scalability from the best Selenium testing platform available.
> Simple to use. Nothing to install. Get started now for free."
> http://p.sf.net/sfu/SauceLabs
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development

Ryan X. Charles
Software Engineer, BitPay
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0xA11B4DDE.asc
Type: application/pgp-keys
Size: 5627 bytes
Desc: not available
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140428/4dded73d/attachment.bin>

More information about the bitcoin-dev mailing list