public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: dentondevelopment <dentondevelopment@protonmail.com>
To: Pavol Rusnak <stick@satoshilabs.com>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] bip48 proposal
Date: Fri, 18 Dec 2020 01:49:07 +0000	[thread overview]
Message-ID: <NGCRT8G5h7uuryz6sQvJd--aNOWJrrCSvKQvjlpHUJOdJlimd72FZAP_kcBa3N7AJpB4DxgldmWD20eUa3iirrRxsebWT0DlFD3ERlaShrM=@protonmail.com> (raw)
In-Reply-To: <cb219d10-64d1-415d-87a0-7b91f3a0af47@Canary>

[-- Attachment #1: Type: text/plain, Size: 1373 bytes --]

Thanks for the link, will certainly be using the provided info as a reference and updating soon.

Regards,
Fontaine

Sent with [ProtonMail](https://protonmail.com) Secure Email.

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Thursday, December 17, 2020 6:58 PM, Pavol Rusnak <stick@satoshilabs.com> wrote:

> 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> 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: 2913 bytes --]

      reply	other threads:[~2020-12-18  1:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-16 12:43 [bitcoin-dev] bip48 proposal 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
2020-12-18  1:49   ` dentondevelopment [this message]

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='NGCRT8G5h7uuryz6sQvJd--aNOWJrrCSvKQvjlpHUJOdJlimd72FZAP_kcBa3N7AJpB4DxgldmWD20eUa3iirrRxsebWT0DlFD3ERlaShrM=@protonmail.com' \
    --to=dentondevelopment@protonmail.com \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    --cc=stick@satoshilabs.com \
    /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