Hello all,
based on some feedback, I've created a pull request with a rewritten
version of BIP 32, hopefully making it more readable:
* Don't reuse the terminology 'public' vs 'private' for the alternate
derivation scheme which doesn't allow computing child public keys from
parent public keys,
Bluetooth, Wifi Direct, HTTP request/responses via broken proxies, smoke
signals... basically anything that is a stream rather than a file.
Right, NFC NDEF and QR codes are not affected, so we can skip the
delimiter for these mediums.
On 01/26/2014 10:24 PM, Mike Hearn wrote:
Which medium is
I think for binding the payment protocol to those transports we should
indeed use protobuf varint length prefixes. But it's unnecessary for all
cases. Unless Gavin feels it'd be better to be consistent everywhere and is
willing to change the spec and code - as far as I know though we're trying
to
To be more accurate, the embedded messages already have length prefixes :-)
On Sun, Jan 26, 2014 at 11:14 PM, Andreas Schildbach
andr...@schildbach.dewrote:
Just keep in mind that if it turns out we need to retrofit messages with
length prefixes I fear we will have to restart with new
4 matches
Mail list logo
