From: Luke Dashjr <luke@dashjr•org>
To: dentondevelopment <dentondevelopment@protonmail•com>
Cc: "bitcoin-dev@lists•linuxfoundation.org"
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] bip48 proposal
Date: Fri, 18 Dec 2020 04:08:30 +0000 [thread overview]
Message-ID: <202012180408.31441.luke@dashjr.org> (raw)
In-Reply-To: <MMFMtQ1lNQcLBIv8haKSpykMjFISWeyYWbFZC7dkzliEZrf2vZYw6ThqFWSYzIntVT3bXvTUol_l-P9wxUIFhwL38lKSGHBFsRG-ukRirP4=@protonmail.com>
Thanks for explaining where instructions are lacking.
How does this look?
https://github.com/bitcoin/bips/pull/1046/files
On Friday 18 December 2020 01:44:27 dentondevelopment wrote:
> Hi Luke,
>
> It looks to have the same motivations and be compatible with
> https://github.com/bitcoin/bips/pull/253 (if I am reading it correctly).
>
> The only guidance I have on proposing a bip is what is on the readme
> https://github.com/bitcoin/bips/blob/master/README.mediawiki
>
> 48 would be fitting if it is unused.
>
> This is still very much a work in progress and there does seem to be
> community support.
>
> Pavol and others have shared relevant info/suggestions which I will be
> using to update the proposal.
>
> Will share again here when the next draft is ready.
>
> Many thanks,
> Fontaine
>
>
> Sent with ProtonMail Secure Email.
>
> ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
>
> On Thursday, December 17, 2020 1:16 AM, Luke Dashjr <luke@dashjr•org> wrote:
> > BIP number 48 has not been assigned. Do not self-assign BIP numbers.
> >
> > Is this intended to be compatible with
> > https://github.com/bitcoin/bips/pull/253 ?
> >
> > Luke
> >
> > On Wednesday 16 December 2020 14:10:28 dentondevelopment via bitcoin-dev
> >
> > wrote:
> > > Here is the repo instead of a static link:
> > > https://github.com/Fonta1n3/bips/blob/master/bip-0048.mediawiki
> > > Fontaine
> > > Sent with ProtonMail Secure Email.
> > > ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
> > > On Wednesday, December 16, 2020 8:43 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
next prev parent reply other threads:[~2020-12-18 4:08 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 [this message]
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
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=202012180408.31441.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--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