1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
|
Return-Path: <dentondevelopment@protonmail.com>
Received: from smtp3.osuosl.org (smtp3.osuosl.org [140.211.166.136])
by lists.linuxfoundation.org (Postfix) with ESMTP id 00419C0001
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 24 Feb 2021 14:02:10 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by smtp3.osuosl.org (Postfix) with ESMTP id E35CD6F5BD
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 24 Feb 2021 14:02:09 +0000 (UTC)
X-Virus-Scanned: amavisd-new at osuosl.org
X-Spam-Flag: NO
X-Spam-Score: 0.601
X-Spam-Level:
X-Spam-Status: No, score=0.601 tagged_above=-999 required=5
tests=[BAYES_50=0.8, DKIM_SIGNED=0.1, DKIM_VALID=-0.1,
DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001,
RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H4=0.001,
RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001]
autolearn=ham autolearn_force=no
Authentication-Results: smtp3.osuosl.org (amavisd-new);
dkim=pass (1024-bit key) header.d=protonmail.com
Received: from smtp3.osuosl.org ([127.0.0.1])
by localhost (smtp3.osuosl.org [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id iOrji0beGSiA
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 24 Feb 2021 14:02:07 +0000 (UTC)
X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0
Received: from mail-40137.protonmail.ch (mail-40137.protonmail.ch
[185.70.40.137])
by smtp3.osuosl.org (Postfix) with ESMTPS id 11307606DF
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 24 Feb 2021 14:02:06 +0000 (UTC)
Date: Wed, 24 Feb 2021 14:02:00 +0000
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com;
s=protonmail; t=1614175323;
bh=nquG3IAVMonry6qDIyh3zpiO9E9iVvtjT2tg7VHqQXw=;
h=Date:To:From:Cc:Reply-To:Subject:In-Reply-To:References:From;
b=QPgZZZiG0hcHZu1ul4KiIi75BqczagkERfC5Wpv3NDjB0hEBCU+E9RZYCSoJN7EUK
ccWuBGbuMU0K+j7RYj0rcwioy84u540sjNDKXHSIQFIAD2emYs9Wgr64Q+Ht1DmQWw
bxLowrNP+KVa2YvGNcr282VcTRSjOcHF4EjNvMmY=
To: Luke Dashjr <luke@dashjr.org>
From: dentondevelopment <dentondevelopment@protonmail.com>
Reply-To: dentondevelopment <dentondevelopment@protonmail.com>
Message-ID: <oHur4CJz2hnPzG4fvsCUZxs33SJgDTF4VeKI9SaK7Og7aYS-xJNWlAjIxGnIgEQ665pr35lZb-_MwVa47BlaOUTVqsM31M2LSlQhKm1_FEc=@protonmail.com>
In-Reply-To: <202012180408.31441.luke@dashjr.org>
References: <cLqW9ZphcaV5hoVNYHjHk_DsdVw_0_hdFxOFwtFkVT9_N_E1IF7ZvtQq745wbqMnny4xzHe8Xdd9TTi2MLyLhB51cI_PJc4fIjLRSpZpGwk=@protonmail.com>
<202012161716.54878.luke@dashjr.org>
<MMFMtQ1lNQcLBIv8haKSpykMjFISWeyYWbFZC7dkzliEZrf2vZYw6ThqFWSYzIntVT3bXvTUol_l-P9wxUIFhwL38lKSGHBFsRG-ukRirP4=@protonmail.com>
<202012180408.31441.luke@dashjr.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-Mailman-Approved-At: Wed, 24 Feb 2021 20:17:45 +0000
Cc: "bitcoin-dev@lists.linuxfoundation.org"
<bitcoin-dev@lists.linuxfoundation.org>
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 <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Feb 2021 14:02:10 -0000
Hello all,
Just wanted to give an update on progress for the "bip48" proposal.
There was some discussion on Twitter between a few multi-sig wallet devs: h=
ttps://twitter.com/fullynoded/status/1339374947228008448?s=3D21
A few key points were brought up:
1. We should not define a `script_type` as a path level
The explicit purpose of this BIP is to define an already existing standard =
that is used in practice across multi-sig wallets. In order to do that we m=
ust define a script_type in the path otherwise "loss of funds" could occur =
and backwards compatibility broken.
2. Another point brought up was that no-one uses the legacy derivation path=
m/48'/0'/0'/1', in practice all "legacy" p2sh multi-sig wallets use bip45.
I agree and have removed all references to legacy p2sh derivations in the p=
roposed bip.
3. We could possibly include a defined "wild card" in the script_type level=
to define any future address types (e.g. taproot)
I agree this could be useful and think Ben Kaufman's suggestion of using m/=
48'/0'/0'/1' for this purpose makes sense, however I also think a future mu=
lti-sig standard for new address types may well be suited for a different B=
IP which could also address concern #1 around including `script_type` at al=
l.
Therefore I have not yet added any mention of "wild card" in the proposed b=
ip but kept strictly to p2sh-p2wsh and p2wsh derivations as used in modern =
day wallets.
I have create a PR https://github.com/bitcoin/bips/pull/1072 so that anyone=
may easily comment on it and any concerns can be raised.
I think the community needs this and it is well over due. I have gotten po=
sitive feedback and support from other devs.
Feedback welcome.
Cheers,
Fontaine
Sent with ProtonMail Secure Email.
=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 Original Me=
ssage =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90
On Friday, December 18, 2020 12:08 PM, Luke Dashjr <luke@dashjr.org> wrote:
> 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.
> > =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 Thursday, December 17, 2020 1:16 AM, Luke Dashjr luke@dashjr.org wro=
te:
> >
> > > 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.
> > > > =E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90=E2=80=90 Ori=
ginal 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
> > >
> > > 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
|
