From: "David A. Harding" <dave@dtrt.org>
To: Andrew Chow <achow101-lists@achow101.com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP Proposals for Output Script Descriptors
Date: Fri, 2 Jul 2021 17:24:05 -1000 [thread overview]
Message-ID: <20210703032405.j3mru5rbag5sbfil@ganymede> (raw)
In-Reply-To: <1eb7b635-094c-a583-7dc0-21cea58ed1fb@achow101.com>
[-- Attachment #1: Type: text/plain, Size: 1197 bytes --]
On Tue, Jun 29, 2021 at 09:14:39PM +0000, Andrew Chow via bitcoin-dev wrote:
> *** Optionally followed by a single <tt>/*</tt> or <tt>/*'</tt> final
> step to denote all direct unhardened or hardened children.
>
> [...]
>
> In the above specification, the hardened indicator <tt>'</tt> may be
> replaced with alternative hardnened indicators of <tt>h</tt> or <tt>H</tt>.
Is there any chance we can take this opportunity to make "h"/"H" the
preferred aliases? Using "'" in bourne-style shells is very
annoying[1], and I suspect it's also creating unnecessary complications
elsewhere.
Alternatives:
- Completely kill "'" (I'd prefer this, but I realize it's complicated
with descriptors already being used widely). If "h"/"H" are made the
preferred aliases, maybe it'd be enough to make implementing "'" a
SHOULD rather than a MUST; this would push implementations towards
displaying descriptors using the h versions for maximum compatibility.
- Calculate the checksum over s/(h|H)/'/ (again, I know that's
complicated with descriptors already widely used)
Thanks,
-Dave
[1] https://github.com/bitcoin/bitcoin/issues/15740#issuecomment-695815432
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-07-03 3:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-29 21:14 [bitcoin-dev] BIP Proposals for Output Script Descriptors Andrew Chow
2021-06-29 22:22 ` Christopher Allen
2021-06-29 22:35 ` Andrew Chow
[not found] ` <CAD5xwhg9sno+aABgUtiwhBo8mLrmj5m9WowGjnUfv-f1pSbshw@mail.gmail.com>
2021-07-02 20:05 ` Andrew Chow
2021-07-03 3:24 ` David A. Harding [this message]
2021-07-03 5:12 ` Andrew Chow
2021-07-03 8:35 ` Craig Raw
2021-07-03 10:05 ` David A. Harding
2021-07-03 14:00 ` Craig Raw
2021-07-04 17:56 ` Daniel Bayerdorffer
2021-08-05 14:27 ` Sjors Provoost
2021-08-05 20:49 ` Christopher Allen
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=20210703032405.j3mru5rbag5sbfil@ganymede \
--to=dave@dtrt.org \
--cc=achow101-lists@achow101.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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