-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
We have BIP70 already in use (over a hundred paid requests).
Could you elaborate on why this needs changing?
On 28-04-14 14:39, Gavin Andresen wrote:
There is a discussion about clarifying how BIP70 signs payment
requests here:
Consensus is the spec should be clarified to match current behavior, so it
won't change.
--
Gavin Andresen
On Apr 29, 2014, at 9:44 AM, Jouke Hofman jo...@bitonic.nl wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
We have BIP70 already in use (over a hundred paid requests).
There is a discussion about clarifying how BIP70 signs payment requests
here:
https://github.com/bitcoin/bips/pull/41
The issue is what to do with the signature field before signing. The code
Mike and I initially wrote does this:
request.set_signature(string());
(sets signature to the
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.
-10 for changing such a basic thing at this point. It'd cause chaos for
the early
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.
5 matches
Mail list logo
