From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from hemlock.osuosl.org (smtp2.osuosl.org [140.211.166.133]) by lists.linuxfoundation.org (Postfix) with ESMTP id 0AD3BC013B for ; Thu, 17 Dec 2020 11:26:16 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by hemlock.osuosl.org (Postfix) with ESMTP id EDBB48792D for ; Thu, 17 Dec 2020 11:26:15 +0000 (UTC) X-Virus-Scanned: amavisd-new at osuosl.org Received: from hemlock.osuosl.org ([127.0.0.1]) by localhost (.osuosl.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xdN5EGK4TdkU for ; Thu, 17 Dec 2020 11:26:15 +0000 (UTC) X-Greylist: delayed 00:28:04 by SQLgrey-1.7.6 Received: from mail-ed1-f49.google.com (mail-ed1-f49.google.com [209.85.208.49]) by hemlock.osuosl.org (Postfix) with ESMTPS id 1A40987928 for ; Thu, 17 Dec 2020 11:26:15 +0000 (UTC) Received: by mail-ed1-f49.google.com with SMTP id c7so28255825edv.6 for ; Thu, 17 Dec 2020 03:26:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=satoshilabs.com; s=google; h=date:from:to:message-id:in-reply-to:references:subject:mime-version; bh=uJjS40NiDcJmcm4961U+/IP9kNHtAvrmM9k7RToiYpo=; b=NyIvv8Ly1wdJz64+HPChvk+oiqy4DqOT/kw46I5jYBMRStvKV6xv7USCcQZ/L4Tzmz OYlO47RD+ZcoH5LpK2GospjDqTYnZgfSmxrK9hpLCn/pccUSClmhEZ2nXPfqexnFo0+O JMoy6PQBxXJ0D2cjRxAdD77rCdxvcE3No05zfV5nl+l+xxprHJCiiLzxu7LnAVD07zDs 2Jk3e0GNJEbVVhS6gK9sIU5xYemNbwS8gYdjxiGtuNxVo+2zDt4Gv07gT6tT++PGPB9F XWVNKmnT0yvIIXt1ds4zKBuO+2LJ6+VpZWejtgfkoJk2VOfG0XBVxvJqKXoGDdhLiv6i rpyw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:message-id:in-reply-to:references :subject:mime-version; bh=uJjS40NiDcJmcm4961U+/IP9kNHtAvrmM9k7RToiYpo=; b=O0BwYLZMeofFHqSOB+pSGd7DIkoH9aEc3L0EijMjfFIMR5/bcylllBGedYvuKpy1cY CupZFOeTTpiuK9WH4KABsfcXamMZQ6nKjXaP2jg6IF0Y7PbNaSjgTFk8tIc9v4OXtTTK dy2lVkZt6bdSL8gGgp4QKr9x3GH6qmopad51hIMsIF7XZ3Rn9yvOzmhWUrM/QBqrxXQw 0TdAeu1BKTbOSdYz4ARFt+ehsvexiIIQGGxwGy5+AyJTT1sBRLWh4XJfmyDKyk+xMZao xd9XxiJLApSo5XgqM1uuAj3xA2MNJuiXKdSw0jmwsOlEvhRAIeaJfZTHPg/rZDIoTqbx Tf6Q== X-Gm-Message-State: AOAM532JHt0qVwHOPFlXim39A3QZM7bD3r1Y5Cqgsiv6WoISn5qMH0S/ 78XFYYZih3z4aOZvFi77Eypbjn2Uyw3ekahY X-Google-Smtp-Source: ABdhPJxdT9/zRLcAb42wv965Q4SjzcvwP2o7oOcgeNqigxOkhmUVoggi2+qPubmmQTpZgsj/GA5OeQ== X-Received: by 2002:aa7:c919:: with SMTP id b25mr36828843edt.108.1608202689906; Thu, 17 Dec 2020 02:58:09 -0800 (PST) Received: from [192.168.2.169] (ip-78-102-52-191.net.upcbroadband.cz. [78.102.52.191]) by smtp.gmail.com with ESMTPSA id ot18sm3441959ejb.54.2020.12.17.02.58.09 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 17 Dec 2020 02:58:09 -0800 (PST) Date: Thu, 17 Dec 2020 11:58:08 +0100 From: Pavol Rusnak To: dentondevelopment , Bitcoin Protocol Discussion Message-ID: In-Reply-To: References: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="5fdb39c0_74b0dc51_2053" 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: Thu, 17 Dec 2020 11:26:16 -0000 --5fdb39c0_74b0dc51_2053 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline I applaud this effort=21 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= =5Ftype=3D0 which is for the raw BIP-11 multisig. While almost not used i= n the wild, it could be imho documented in this proposed BIP as well. =E2=80=94 Best Regards / S pozdravom, Pavol =E2=80=9Cstick=E2=80=9D Rusnak Co-founder and CTO, SatoshiLabs > On Wednesday, Dec 16, 2020 at 2:48 PM, dentondevelopment via bitcoin-de= v wrote: > Hello, > > I would like to propose bip48 (taking bip44 as inspiration), with the p= urpose of documenting modern multi-sig derivations. > > Please see a rough draft of the proposed bip attached, comments/input w= elcome. > > Regards, > =46ontaine > > > =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F= =5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F=5F > bitcoin-dev mailing list > bitcoin-dev=40lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev --5fdb39c0_74b0dc51_2053 Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline <= meta name=3D=22viewport=22 content=3D=22width=3Ddevice-width, initial-sca= le=3D1.0, user-scalable=3Dno=22>
I applaud this effort=21

We tried to doc= ument the 48 path usage in this document:


The only difference I = can spot is that our document also documents script=5Ftype=3D0 which is f= or the raw BIP-11 multisig. While almost not used in the wild, it could b= e imho documented in this proposed BIP as well.

=E2=80=94
Best Regards / S= pozdravom,

Pavol =E2=80=9Cstick=E2= =80=9D Rusnak
Co-founder and CTO, SatoshiLabs

=
= --5fdb39c0_74b0dc51_2053--