From: Pavol Rusnak <stick@satoshilabs•com>
To: Andrew Chow <achow101-lists@achow101•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: Wed, 27 Jul 2022 10:44:36 +0200 [thread overview]
Message-ID: <CAF90AvkZWqRv_hwj2qacOZjpSjdenb-51PcXFgAG4Z985m7BBQ@mail.gmail.com> (raw)
In-Reply-To: <c04b2ed0-d50e-9921-2aa4-b1534fca14a0@achow101.com>
[-- Attachment #1: Type: text/plain, Size: 661 bytes --]
On Wed, 27 Jul 2022 at 00:28, Andrew Chow <achow101-lists@achow101•com>
wrote:
> However I don't see why this couldn't generalize to any sized tuples. As
> long as the tuples are all the same length, and the limit is one tuple per
> key expression, then we don't get any combinatorial blowup issues.
>
I think it's worthwhile to generalize for any sized tuples. I don't have
any existing particular use case in mind, because BIP-44, BIP-84, etc. are
fine with just using <0;1>, but there might be some upcoming standards in
the future that will want to introduce more sub-paths.
--
Best Regards / S pozdravom,
Pavol "stick" Rusnak
Co-Founder, SatoshiLabs
[-- Attachment #2: Type: text/html, Size: 1211 bytes --]
next prev parent reply other threads:[~2022-07-27 8:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 22:27 Andrew Chow
2022-07-27 8:44 ` Pavol Rusnak [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-07-27 14:58 Andrew Chow
2022-07-28 9:40 ` Dmitry Petukhov
2022-08-04 1:16 ` Billy Tetrud
2022-08-04 7:09 ` Dmitry Petukhov
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=CAF90AvkZWqRv_hwj2qacOZjpSjdenb-51PcXFgAG4Z985m7BBQ@mail.gmail.com \
--to=stick@satoshilabs$(echo .)com \
--cc=achow101-lists@achow101$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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