MIME-Version: 1.0
In-Reply-To: <CAMZUoK=sZ_b3SM1qiPfEF8uMRPCoY4LKcXit4Nd5Kb_aS9cVJQ@mail.gmail.com>
References: <CAPg+sBh0sFA7b6a+48Oojwy655GB9W6Th8JiCpd+2ruQjPev8Q@mail.gmail.com>
	<CAPg+sBiPiLHZFoYY=gs6LT+Q2Kb5NmbVU05u7c+0WRPjveBJhQ@mail.gmail.com>
	<CAPg+sBjFC98WzB+eCCcBOg0c-y+aj=_+-+PYyOO-7CA1xe7HAw@mail.gmail.com>
	<CAMZUoK=sZ_b3SM1qiPfEF8uMRPCoY4LKcXit4Nd5Kb_aS9cVJQ@mail.gmail.com>
From: "Russell O'Connor" <roconnor@blockstream.io>
Date: Thu, 26 Jul 2018 10:31:30 -0400
Message-ID: <CAMZUoKmsGkm56AktXK7yVkCNoMHgN_+pW9DrbGSrwx=2=a9+ig@mail.gmail.com>
To: Pieter Wuille <pieter.wuille@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000144c020571e7db0a"
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] A BIP proposal for segwit addresses
Precedence: list

--000000000000144c020571e7db0a
Content-Type: text/plain; charset="UTF-8"

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'Connor <roconnor@blockstream.io>
wrote:

> 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
> applications.
>
> You should also add to this section that the HRP should be lowercase.
>
> Since Bech32 forbids mixed-case and otherwise converts everything to
> lowercase, it is good to warn upfront against using uppercase in the HRP.
>
> I know the BIP is marked as final, but this wouldn't be a normative change.
>

--000000000000144c020571e7db0a
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>I think I phrased this badly.</div><div><br></div><di=
v>What I mean is that there should be a note that HRP should be specified i=
n lowercase, or at least mention that uppercase and lowercase HRPs are cons=
idered equivalent and will be canonicalized to lowercase during validation.=
<br></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Thu,=
 Jul 26, 2018 at 9:43 AM, Russell O&#39;Connor <span dir=3D"ltr">&lt;<a hre=
f=3D"mailto:roconnor@blockstream.io" target=3D"_blank">roconnor@blockstream=
.io</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr=
"><div>Hi Pieter,</div><div><br></div><div>&gt; The <b>human-readable part<=
/b>, which is intended to convey the type of=20
data, or anything else that is relevant to the reader. This part MUST=20
contain 1 to 83 US-ASCII characters, with each character having a value=20
in the range [33-126]. HRP validity may be further restricted by=20
specific applications.<br></div><div><br></div><div>You should also add to =
this section that the HRP should be lowercase.</div><div><br></div><div>Sin=
ce Bech32 forbids mixed-case and otherwise converts everything to lowercase=
, it is good to warn upfront against using uppercase in the HRP.</div><div>=
<br></div><div>I know the BIP is marked as final, but this wouldn&#39;t be =
a normative change.<br></div></div>
</blockquote></div><br></div></div>

--000000000000144c020571e7db0a--