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
|
Return-Path: <root@haskoin.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id A054E1997
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 5 Oct 2015 19:36:14 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from imap11-3.ox.privateemail.com (imap11-3.ox.privateemail.com
[198.187.29.245])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 4E68519A
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 5 Oct 2015 19:36:14 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
by imap11.ox.privateemail.com (Postfix) with ESMTP id 0A586880114;
Mon, 5 Oct 2015 15:36:10 -0400 (EDT)
X-Virus-Scanned: Debian amavisd-new at imap11.ox.privateemail.com
Received: from imap11.ox.privateemail.com ([127.0.0.1])
by localhost (imap11.ox.privateemail.com [127.0.0.1]) (amavisd-new,
port 10024)
with LMTP id jhY1I35fCGZr; Mon, 5 Oct 2015 15:36:09 -0400 (EDT)
Received: from [192.168.44.30] (unknown [95.83.250.47])
(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
(No client certificate requested)
by imap11.ox.privateemail.com (Postfix) with ESMTPSA id 42FD38800DA;
Mon, 5 Oct 2015 15:36:07 -0400 (EDT)
To: Jonas Schnelli <dev@jonasschnelli.ch>,
Matias Alejo Garcia <matias@bitpay.com>,
Thomas Kerin <thomas.kerin@gmail.com>
References: <CABQSq2Q98K5zbUbQAqSE4OYez2QuOaWTt+9n5iZmSR2boynf_Q@mail.gmail.com>
<560FCD30.9020902@haskoin.com> <5611432F.5070209@haskoin.com>
<561160EB.30505@gmail.com>
<CA+vKqYeBDHEGRgCsuAp3wQKb9idH085e5K3uNdeRLFvc9MTpdQ@mail.gmail.com>
<56126AB0.3030107@haskoin.com> <56126DF8.20602@jonasschnelli.ch>
From: Jean-Pierre Rupp <root@haskoin.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <5612D125.8000102@haskoin.com>
Date: Mon, 5 Oct 2015 20:36:05 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <56126DF8.20602@jonasschnelli.ch>
Content-Type: multipart/signed; micalg=pgp-sha256;
protocol="application/pgp-signature";
boundary="7k1soU01hECRiMlk6ftv0OspMnhprnjx3"
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham
version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Cc: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] [Bitcoin-development] New BIP32 structure for
P2SH multisig wallets [BIP-45]
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development 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: Mon, 05 Oct 2015 19:36:14 -0000
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--7k1soU01hECRiMlk6ftv0OspMnhprnjx3
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Sure,
You always have these alternatives, but the problem is that it starts to
become harder to restore your wallet from the initial mnemonic if
something goes wrong.
Say you lose all your wallet information except for your mnemonic,
extended public keys from all people you established multi-signature
accounts with, and you know which arrangement you had with each of your
cosigners (2-of-3, 2-of-2, etc.). Your software will not have a hard
time rebuilding all accounts from information obtained from the public
blockchain. Adding a new dimension, here the i' derivation, will make
things harder. You would need to know this piece of data too.
Another good thing about using the same derivation always is that you
can give every cosigner only that single piece of information, that
single xpub, in order to establish multisig relationships. There is no
need to use a different one per relationship. This simplifies the
workflow for establishing new multi-signature accounts significantly.
Greetings
On 05/10/15 13:32, Jonas Schnelli wrote:
> What holds you back from using m/i'/45' where i' is your multisig
> "account" number?
>=20
> Within your BIP45 wallet (lets assume Copay), you would not provide
> the xpubkey at m/45', instead you would provide your xpubkey at m/i'/45=
'
> .
>=20
> It's probably no longer pure BIP45.
--7k1soU01hECRiMlk6ftv0OspMnhprnjx3
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQEcBAEBCAAGBQJWEtElAAoJEF1L4IYxCopbpp8H/R1gbk7ngDr/hn5Qn5DQm1K9
VZdmKtudFUrndsXP9JxaDJRwv4rpq1MXwE6QKSZHhFCc7mN5Y8dPbtoClgP6Vn1U
GUKFuEkehdLBbumO85JoUZFB+xi9x0wkLfhRBpYizo3/gBtWWtA/b59vJs+0fLc+
RFaXyTLIwKGQXS39LTGvOdzsxhm0tK1l5YeDf3YXC66lQs8FowgHd4Eus4JGGu9V
56lFGDOO6XOktmQ2ujvVaDBtZJNcF5B09QYi1o6HMr7px9Fts8U1+Md8CApWpL2E
1AsleX5UWD8HDXrZY5L7FPqiH9DXOc8b8zIb1BG6muMD2zNbeEh4W5w/cfE20bY=
=ZS0N
-----END PGP SIGNATURE-----
--7k1soU01hECRiMlk6ftv0OspMnhprnjx3--
|
