From: "Ryan X. Charles" <ryan@bitpay•com>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Proposal to change payment protocol signing
Date: Mon, 28 Apr 2014 16:53:41 -0400 [thread overview]
Message-ID: <535EBFD5.1060806@bitpay.com> (raw)
In-Reply-To: <CANEZrP1_FtEU3Pf3CibMg3YWn8Jn8E7GEj9_x9b3Ym4_yL-ZfA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1351 bytes --]
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@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
--
Ryan X. Charles
Software Engineer, BitPay
[-- Attachment #2: 0xA11B4DDE.asc --]
[-- Type: application/pgp-keys, Size: 5627 bytes --]
next prev parent reply other threads:[~2014-04-28 20:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-28 12:39 Gavin Andresen
2014-04-28 16:14 ` Mike Hearn
2014-04-28 20:53 ` Ryan X. Charles [this message]
2014-04-29 16:44 ` Jouke Hofman
2014-04-29 19:12 ` Gavin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=535EBFD5.1060806@bitpay.com \
--to=ryan@bitpay$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox