From: "David A. Harding" <dave@dtrt•org>
To: Dmitry Petukhov <dp@simplexum•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP draft: BIP32 Path Templates
Date: Fri, 3 Jul 2020 10:39:45 -0400 [thread overview]
Message-ID: <20200703143945.kvuczb7z4vr6ehwr@ganymede> (raw)
In-Reply-To: <20200702212839.2d59e435@simplexum.com>
[-- Attachment #1: Type: text/plain, Size: 848 bytes --]
On Thu, Jul 02, 2020 at 09:28:39PM +0500, Dmitry Petukhov via bitcoin-dev wrote:
> I think there should be standard format to describe constraints for
> BIP32 paths.
>
> I present a BIP draft that specifies "path templates" for BIP32 paths:
>
> https://github.com/dgpv/bip32_template_parse_tplaplus_spec/blob/master/bip-path-templates.mediawiki
Hi Dmitry,
How do path templates compare to key origin identification[1] in
output script descriptors?
Could you maybe give a specfic example of how path templates might be
used? Are they for backups? Multisig wallet coordination? Managing
data between software transaction construction and hardware device
signing?
Thanks,
-Dave
[1] https://github.com/bitcoin/bitcoin/blob/master/doc/descriptors.md#key-origin-identification
(See earlier in the doc for examples)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-07-03 14:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-02 16:28 Dmitry Petukhov
2020-07-03 14:39 ` David A. Harding [this message]
2020-07-03 16:53 ` Dmitry Petukhov
2020-07-03 19:10 ` Dmitry Petukhov
2020-07-06 15:24 ` Dmitry Petukhov
2020-10-26 13:04 ` Dmitry Petukhov
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=20200703143945.kvuczb7z4vr6ehwr@ganymede \
--to=dave@dtrt$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=dp@simplexum$(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