Re: [bitcoin-dev] A BIP proposal for segwit addresses

2018-07-26 Thread Russell O'Connor via bitcoin-dev
I think I phrased this badly. What I mean is that there should be a note that HRP should be specified in lowercase, or at least mention that uppercase and lowercase HRPs are considered equivalent and will be canonicalized to lowercase during validation. On Thu, Jul 26, 2018 at 9:43 AM, Russell O'

Re: [bitcoin-dev] A BIP proposal for segwit addresses

2018-07-26 Thread Russell O'Connor via bitcoin-dev
Hi Pieter, > The *human-readable part*, which is intended to convey the type of data, or anything else that is relevant to the reader. This part MUST contain 1 to 83 US-ASCII characters, with each character having a value in the range [33-126]. HRP validity may be further restricted by specific ap

Re: [bitcoin-dev] A BIP proposal for segwit addresses

2017-05-20 Thread Pieter Wuille via bitcoin-dev
On Sun, May 7, 2017 at 2:39 PM, Pieter Wuille wrote: > I'd like to move forward and request a BIP number assignment for this > proposal. The proposal has been submitted as BIP173: https://github.com/bitcoin/bips/blob/master/bip-0173.mediawiki Cheers, -- Pieter _

Re: [bitcoin-dev] A BIP proposal for segwit addresses

2017-05-07 Thread Peter Todd via bitcoin-dev
On Sun, May 07, 2017 at 02:39:14PM -0700, Pieter Wuille via bitcoin-dev wrote: > > I don't understand your comment about non-english speaking users. > Obviously they cannot voice-communicate at all with only-english-speaking > users, so there is no need to communicate voice-communicate addresses >

Re: [bitcoin-dev] A BIP proposal for segwit addresses

2017-05-07 Thread Pieter Wuille via bitcoin-dev
On Mon, Mar 20, 2017 at 2:35 PM, Pieter Wuille wrote: > Hello everyone, > > You can find the text here: > https://github.com/sipa/bech32/blob/master/bip-witaddr.mediawiki > Responding to a few comments: By Andreas Schildbach: > I'm not convinced that transmitting addresses via voice should be

Re: [bitcoin-dev] A BIP proposal for segwit addresses

2017-03-29 Thread Lucas Ontivero via bitcoin-dev
I don't know if i should response to this mail list or make a comment in commit file ( https://github.com/sipa/bech32/commit/52b5a0fa6d3174c4150393fb7d6b58d34b4f5e0b#diff-d23a42e5c904045098e8f8b1189f481e ) * Motivation: Here I think it could worth to mention that 58 requires mathematical operatio

Re: [bitcoin-dev] A BIP proposal for segwit addresses

2017-03-29 Thread Andreas Schildbach via bitcoin-dev
On 03/21/2017 08:14 PM, Peter Todd via bitcoin-dev wrote: > On Tue, Mar 21, 2017 at 05:16:30PM +0100, Andreas Schildbach via bitcoin-dev > wrote: >> Why use Base 32 when the QR code alphanumeric mode allows 44 characters? >> In Bitcoin Wallet, I use Base 43 (alphabet: >> "0123456789ABCDEFGHIJKLMNO

Re: [bitcoin-dev] A BIP proposal for segwit addresses

2017-03-21 Thread Peter Todd via bitcoin-dev
On Tue, Mar 21, 2017 at 05:16:30PM +0100, Andreas Schildbach via bitcoin-dev wrote: > Why use Base 32 when the QR code alphanumeric mode allows 44 characters? > In Bitcoin Wallet, I use Base 43 (alphabet: > "0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ$*+-./:") for most efficient QR > code encoding. I onl

Re: [bitcoin-dev] A BIP proposal for segwit addresses

2017-03-21 Thread Andreas Schildbach via bitcoin-dev
Why use Base 32 when the QR code alphanumeric mode allows 44 characters? In Bitcoin Wallet, I use Base 43 (alphabet: "0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ$*+-./:") for most efficient QR code encoding. I only leave out the space character because it gets replaced by "+" in URLs. On 03/20/2017 10:3