From: Pavol Rusnak <stick@satoshilabs•com>
To: dentondevelopment <dentondevelopment@protonmail•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] bip48 proposal
Date: Thu, 17 Dec 2020 11:58:08 +0100 [thread overview]
Message-ID: <cb219d10-64d1-415d-87a0-7b91f3a0af47@Canary> (raw)
In-Reply-To: <cLqW9ZphcaV5hoVNYHjHk_DsdVw_0_hdFxOFwtFkVT9_N_E1IF7ZvtQq745wbqMnny4xzHe8Xdd9TTi2MLyLhB51cI_PJc4fIjLRSpZpGwk=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 1091 bytes --]
I applaud this effort!
We tried to document the 48 path usage in this document:
https://github.com/trezor/trezor-firmware/blob/master/docs/misc/purpose48.md
The only difference I can spot is that our document also documents script_type=0 which is for the raw BIP-11 multisig. While almost not used in the wild, it could be imho documented in this proposed BIP as well.
—
Best Regards / S pozdravom,
Pavol “stick” Rusnak
Co-founder and CTO, SatoshiLabs
> On Wednesday, Dec 16, 2020 at 2:48 PM, dentondevelopment via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org (mailto:bitcoin-dev@lists•linuxfoundation.org)> wrote:
> Hello,
>
> I would like to propose bip48 (taking bip44 as inspiration), with the purpose of documenting modern multi-sig derivations.
>
> Please see a rough draft of the proposed bip attached, comments/input welcome.
>
> Regards,
> Fontaine
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists•linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
[-- Attachment #2: Type: text/html, Size: 2430 bytes --]
next prev parent reply other threads:[~2020-12-17 11:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 12:43 dentondevelopment
2020-12-16 14:10 ` dentondevelopment
2020-12-16 17:16 ` Luke Dashjr
2020-12-16 18:48 ` Keagan McClelland
2020-12-18 1:44 ` dentondevelopment
2020-12-18 4:08 ` Luke Dashjr
2021-02-24 14:02 ` dentondevelopment
2021-02-25 10:23 ` Craig Raw
2020-12-17 10:58 ` Pavol Rusnak [this message]
2020-12-18 1:49 ` dentondevelopment
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=cb219d10-64d1-415d-87a0-7b91f3a0af47@Canary \
--to=stick@satoshilabs$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=dentondevelopment@protonmail$(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