From: "Russell O'Connor" <roconnor@blockstream•io>
To: Pieter Wuille <pieter.wuille@gmail•com>
Cc: Bitcoin Dev <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] A BIP proposal for segwit addresses
Date: Thu, 26 Jul 2018 10:31:30 -0400 [thread overview]
Message-ID: <CAMZUoKmsGkm56AktXK7yVkCNoMHgN_+pW9DrbGSrwx=2=a9+ig@mail.gmail.com> (raw)
In-Reply-To: <CAMZUoK=sZ_b3SM1qiPfEF8uMRPCoY4LKcXit4Nd5Kb_aS9cVJQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 969 bytes --]
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.
>
[-- Attachment #2: Type: text/html, Size: 1441 bytes --]
prev parent reply other threads:[~2018-07-26 14:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 21:35 Pieter Wuille
2017-03-21 16:16 ` Andreas Schildbach
2017-03-21 19:14 ` Peter Todd
2017-03-29 10:07 ` Andreas Schildbach
2017-03-30 4:50 ` Lucas Ontivero
2017-05-07 21:39 ` Pieter Wuille
2017-05-07 22:34 ` Peter Todd
2017-05-20 20:13 ` Pieter Wuille
2018-07-26 13:43 ` Russell O'Connor
2018-07-26 14:31 ` Russell O'Connor [this message]
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='CAMZUoKmsGkm56AktXK7yVkCNoMHgN_+pW9DrbGSrwx=2=a9+ig@mail.gmail.com' \
--to=roconnor@blockstream$(echo .)io \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=pieter.wuille@gmail$(echo .)com \
/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