From: Dmitry Petukhov <dp@simplexum.com>
To: Dmitry Petukhov via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP draft: BIP32 Path Templates
Date: Mon, 6 Jul 2020 20:24:27 +0500 [thread overview]
Message-ID: <20200706202427.5fcffc3c@simplexum.com> (raw)
In-Reply-To: <20200703215344.349376cd@simplexum.com>
[-- Attachment #1: Type: text/plain, Size: 407 bytes --]
В Fri, 3 Jul 2020 21:53:44 +0500
Dmitry Petukhov via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org>
wrote:
> My hope is that having a clear specification and (possibly, in the
> future) permissibly licensed quality implementations would make
> adopting such format easier for vendors.
I have added a C implementation (MIT-licensed):
https://github.com/dgpv/bip32_template_c_implementation
[-- Attachment #2: Цифровая подпись OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-07-06 15:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-02 16:28 [bitcoin-dev] BIP draft: BIP32 Path Templates Dmitry Petukhov
2020-07-03 14:39 ` David A. Harding
2020-07-03 16:53 ` Dmitry Petukhov
2020-07-03 19:10 ` Dmitry Petukhov
2020-07-06 15:24 ` Dmitry Petukhov [this message]
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=20200706202427.5fcffc3c@simplexum.com \
--to=dp@simplexum.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