From: Dmitry Petukhov <dp@simplexum.com>
To: Billy Tetrud <billy.tetrud@gmail.com>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP Proposal: Receiving and Change Derivation Paths in a Single Descriptor
Date: Thu, 4 Aug 2022 09:09:33 +0200 [thread overview]
Message-ID: <20220804090933.228ad190@simplexum.com> (raw)
In-Reply-To: <CAGpPWDaSsAn3GPoYdJmdJ6iW6M6G_2G8ua1cONhjSRRdSog8Pg@mail.gmail.com>
В Wed, 3 Aug 2022 20:16:52 -0500
Billy Tetrud <billy.tetrud@gmail.com> wrote:
> A descriptor format is simply defining a space of address
> derivation paths. It is not describing in any way what each path is
> intended for - those are conventions outside the scope of this BIP
> IMO. Defining the conventions of derivation path indexes should be a
> separate BIP. Single responsibility principle.
I see, you're right. I misread the BIP proposal text and missed that it
describes 'receive' and 'change' only as 'common usecase', not as
definitive designations for indexes. Considering this, I too see no need
to include such conventions in this BIP.
next prev parent reply other threads:[~2022-08-04 7:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 14:58 [bitcoin-dev] BIP Proposal: Receiving and Change Derivation Paths in a Single Descriptor Andrew Chow
2022-07-28 9:40 ` Dmitry Petukhov
2022-08-04 1:16 ` Billy Tetrud
2022-08-04 7:09 ` Dmitry Petukhov [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-07-26 22:27 Andrew Chow
2022-07-27 8:44 ` Pavol Rusnak
2022-07-26 21:41 Andrew Chow
2022-07-26 21:56 ` Pavol Rusnak
2022-07-27 7:57 ` Craig Raw
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=20220804090933.228ad190@simplexum.com \
--to=dp@simplexum.com \
--cc=billy.tetrud@gmail.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