From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from whitealder.osuosl.org (smtp1.osuosl.org [140.211.166.138]) by lists.linuxfoundation.org (Postfix) with ESMTP id 2AFFDC013B for ; Wed, 16 Dec 2020 18:49:00 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by whitealder.osuosl.org (Postfix) with ESMTP id C0B4285C4C for ; Wed, 16 Dec 2020 18:48:46 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org Received: from whitealder.osuosl.org ([127.0.0.1]) by localhost (.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2kl+CTkV8fFS for ; Wed, 16 Dec 2020 18:48:44 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-ej1-f53.google.com (mail-ej1-f53.google.com [209.85.218.53]) by whitealder.osuosl.org (Postfix) with ESMTPS id A622B85BBA for ; Wed, 16 Dec 2020 18:48:43 +0000 (UTC) Received: by mail-ej1-f53.google.com with SMTP id x16so34253088ejj.7 for ; Wed, 16 Dec 2020 10:48:43 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=3GDPOtx7QZGvxVDUH6w0ywfZyQnsA7+DCdnol4t4nLc=; b=Hi0hY8Z33NnVYBJz7G3n6Nt1SdogEKdJx2WbrAkcdEEMgNforOv1X7UV0QMOjk1Ip1 DASdCWhbtxr/eJQQOp5aMe5Wq8jANVFVM0yBFHoJ875lQ/NkWb3mdD32t4mwIhc+0X4F WjG1n/Ug2t9X9SliwdrAAvIVg5iMvBXBjj3lSyHxUPF42ApvlG+O9YIIZdBF53E9KirI 3QB2JPgM1Mr6VZLPozWTFOjbb1pqjtUYgCCDCEFKvjPF+hIbnOG3LQ0FxohbRYprE+W7 Vzx9mkA6soyGlYfZ/kS+wieOZHZEbHNYoNjyLDIz3bUvn+AxQq8FoSFQ9+zv9U4G5Hdg SAgg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=3GDPOtx7QZGvxVDUH6w0ywfZyQnsA7+DCdnol4t4nLc=; b=fFrhPzxZY6y+x+4AXWKWoRxGdrjbr2YDB9T6BlcUOLIGhQ2m7nwYcjbZ2GH3J8Sm1O SZoQgb1Uhv7V0EOvypFJY3qF8yONHVe4iBvdk1ecWBE2lZ7uY1V/ze+Q0k/LuAzleqt9 rVoCJXQpuhHlrKwVasljZm9a7RcQKtfBdrk68Go+cWXt8gB2aSN64QfpA0h2LJDBzuWS jFd6hSnMyV3qf/KUwg0KbAKcE+U1yUQM5cemw9W+EynG1syUb88Vy6uZnAsHHh7O8bt4 7+gVK1Lxetf5FjR13YmjIfa0kbxa9+sgFgv9M1BKyXPr7kR+63mixs4tQ5/1Ls1y7YKV 4m2g== X-Gm-Message-State: AOAM531oRYe7hY5ZqKM/VTjRhZr6wf6TaRqigBzYXa2yNM09zO96/QnB vA02MXPksFcRdfhzog9H1ln8Avc/WjYcFzDZESk= X-Google-Smtp-Source: ABdhPJwatJZYEn8UA7kfbffWFjOc+1NJai73WC574RA16GAANSpFYyfMN+CuNUTokxrLn80QQ5jeEm0da9sh5u6zQ5g= X-Received: by 2002:a17:906:b2da:: with SMTP id cf26mr2956105ejb.176.1608144522036; Wed, 16 Dec 2020 10:48:42 -0800 (PST) MIME-Version: 1.0 References: <1_mYgDaVRKZIADl9fWVzTYGNBr0Z43Fp-Gcoz2ibhKY4VKAk1Vbs9XSZ3rlzyGEwvE2YEOn2C0IxAVKkr_rr6KX0YxMiNTiTtQVBL4vgyd8=@protonmail.com> <202012161716.54878.luke@dashjr.org> In-Reply-To: <202012161716.54878.luke@dashjr.org> From: Keagan McClelland Date: Wed, 16 Dec 2020 11:48:30 -0700 Message-ID: To: Luke Dashjr , Bitcoin Protocol Discussion Content-Type: multipart/alternative; boundary="000000000000fbc7fb05b69952e5" X-Mailman-Approved-At: Wed, 16 Dec 2020 19:47:16 +0000 Subject: Re: [bitcoin-dev] bip48 proposal X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: Bitcoin Protocol Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Dec 2020 18:49:00 -0000 --000000000000fbc7fb05b69952e5 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable I was just looking into the conventions around this yesterday! It seems like this proposal is mostly just formalizing stuff that is already a tacit standard. I'm glad to see that someone is documenting it somewhere more "official". It appears consistent with https://github.com/bitcoin/bips/pull/253, Howeve= r, due to historical timing, the PR you linked doesn't include any standards around segwit conventions. In the review thread you had mentioned that you needed an ACK from prusnak, but he explicitly gave a NACK in favor of a separate proposal for BIP 48, which seems like it could be something like the OP. Reading the proposal it seems consistent with the pull request that you linked, as well. At the end of the thread the author of PR#253 said they would open a separate proposal, but it appears that it never materialized. Was there a reason for this? Keagan On Wed, Dec 16, 2020 at 10:17 AM Luke Dashjr via bitcoin-dev < bitcoin-dev@lists.linuxfoundation.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](https://protonmail.com) Secure Email. > > > > =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 Origina= l Message =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 > > > > On Wednesday, December 16, 2020 8:43 PM, dentondevelopment via > bitcoin-dev > 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 > --000000000000fbc7fb05b69952e5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I was just looking into the conventions around this y= esterday! It seems like this proposal is mostly just formalizing stuff that= is already a tacit standard. I'm glad to see that someone is documenti= ng it somewhere more "official".

It appears c= onsistent with=C2=A0https://github.com/bitcoin/bips/pull/253= ,=C2=A0However, due to historical timing, the PR you linked doesn't= include any standards around segwit conventions.

In the= review thread you had mentioned that you needed an ACK from prusnak, but h= e explicitly gave a NACK in favor of a separate proposal for BIP 48, which = seems like it could be something like the OP. Reading=C2=A0the proposal it = seems consistent with the pull request that you linked, as well. At the end= of the thread the author of PR#253 said they would open a separate proposa= l, but it appears that it never materialized. Was there a reason for this?<= /div>

Keagan

<= div dir=3D"ltr" class=3D"gmail_attr">On Wed, Dec 16, 2020 at 10:17 AM Luke = Dashjr via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org> wrote:
BIP number 48 has not been as= signed. 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](https://protonmail.com) Secure Email.
>
> =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 Origin= al Message =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90<= br> >
> 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/i= nput
> > welcome.
> >
> > Regards,
> > Fontaine

_______________________________________________
bitcoin-dev mailing list
= bitcoin-dev@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mail= man/listinfo/bitcoin-dev
--000000000000fbc7fb05b69952e5--