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
|
Return-Path: <dev@jonasschnelli.ch>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id CD9A2722
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 14 May 2016 08:16:48 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from server3 (server3.include7.ch [144.76.194.38])
by smtp1.linuxfoundation.org (Postfix) with ESMTP id 1156E16F
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 14 May 2016 08:16:48 +0000 (UTC)
Received: by server3 (Postfix, from userid 115)
id BFEAC2E6051F; Sat, 14 May 2016 10:16:46 +0200 (CEST)
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
X-Spam-Level:
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00, FSL_HELO_NON_FQDN_1
autolearn=ham version=3.3.1
Received: from Jonass-MacBook-Pro.local (unknown [213.55.184.183])
by server3 (Postfix) with ESMTPSA id 090812D0046E
for <bitcoin-dev@lists.linuxfoundation.org>;
Sat, 14 May 2016 10:16:45 +0200 (CEST)
To: bitcoin-dev@lists.linuxfoundation.org
References: <5735D3A4.7090608@mycelium.com> <5735EC17.5040901@satoshilabs.com>
<CACq0ZD4BvvCryYmO-J9Rof-ogQJ1wNLgmUEU596nuTH=-U8Hag@mail.gmail.com>
<5735FC99.5090001@satoshilabs.com>
<CACq0ZD7mLCaoGpcVEp7NfW=6nsEA39tZp+G8oeySygMEyhuwQA@mail.gmail.com>
<57361577.7060207@satoshilabs.com>
<CACq0ZD7BUaMnRgpx0ZxZu1Ok5weiJ9tbZnyFpXEHsTi==V_t_w@mail.gmail.com>
From: Jonas Schnelli <dev@jonasschnelli.ch>
Message-ID: <5736DEEA.5030603@jonasschnelli.ch>
Date: Sat, 14 May 2016 10:16:42 +0200
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:38.0)
Gecko/20100101 Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <CACq0ZD7BUaMnRgpx0ZxZu1Ok5weiJ9tbZnyFpXEHsTi==V_t_w@mail.gmail.com>
Content-Type: multipart/signed; micalg=pgp-sha256;
protocol="application/pgp-signature";
boundary="GDUukifCTtE2ow6FsDqlqHOkICEh1iSTx"
Subject: Re: [bitcoin-dev] Bip44 extension for P2SH/P2WSH/...
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
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: Sat, 14 May 2016 08:16:49 -0000
This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--GDUukifCTtE2ow6FsDqlqHOkICEh1iSTx
Content-Type: multipart/mixed; boundary="0LrkrpVUs2KiprMXfav1IMAUDDRxrrqjG"
From: Jonas Schnelli <dev@jonasschnelli.ch>
To: bitcoin-dev@lists.linuxfoundation.org
Message-ID: <5736DEEA.5030603@jonasschnelli.ch>
Subject: Re: [bitcoin-dev] Bip44 extension for P2SH/P2WSH/...
References: <5735D3A4.7090608@mycelium.com> <5735EC17.5040901@satoshilabs.com>
<CACq0ZD4BvvCryYmO-J9Rof-ogQJ1wNLgmUEU596nuTH=-U8Hag@mail.gmail.com>
<5735FC99.5090001@satoshilabs.com>
<CACq0ZD7mLCaoGpcVEp7NfW=6nsEA39tZp+G8oeySygMEyhuwQA@mail.gmail.com>
<57361577.7060207@satoshilabs.com>
<CACq0ZD7BUaMnRgpx0ZxZu1Ok5weiJ9tbZnyFpXEHsTi==V_t_w@mail.gmail.com>
In-Reply-To: <CACq0ZD7BUaMnRgpx0ZxZu1Ok5weiJ9tbZnyFpXEHsTi==V_t_w@mail.gmail.com>
--0LrkrpVUs2KiprMXfav1IMAUDDRxrrqjG
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
Hi
> That's a valid concern, but I don't see the conflict here. In order to
> recover funds from a wallet conforming to BIPXX, you must have wallet
> software that handles BIPXX. Simply making BIPXX backwards compatible
> with previously created BIP44 or BIP43 purpose 0 wallets doesn't change=
> this at all.
Maybe I'm going a bit offtopic. Sorry for that.
Importing a bip32 wallet (bip44 or not) is still an expert job IMO.
Also importing can lead to bad security practice (especially without a
sweep).
Users will send around xpriv or import an seed over a compromised
computer to a cold storage, etc.
I don't think users want to import private keys.
They probably want to import the transaction history and send all funds
covered by that seed to a new wallet.
I often though that task is better covered by a little GUI tool or
cli-app/script:
-> Accept different bip32 schematics (bip32 native, bip44, etc.)
-> Accept different bip39 (like) implementation
-> Create large lookup windows
-> Create a sweep transaction to a new address/wallet and sign/broadcast =
it.
-> Export transaction history (CSV)
But maybe I'm over-complicating things.
--
</jonas>
--0LrkrpVUs2KiprMXfav1IMAUDDRxrrqjG--
--GDUukifCTtE2ow6FsDqlqHOkICEh1iSTx
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
iQIcBAEBCAAGBQJXNt7qAAoJECnUvLZBb1Psaz4P/jfpi05r19bsupFZWzU3fPWa
5TT+pvlej3gj0qbsBnLy3pPSSRjibtKVXyTIvp9Aq2j9OJOkIN5q3Y4EOtFjAo5g
B6AiDP0NC/3438oX2ImXpbL54Yii5i8/lGStCdIDIX6nC59fDNJS7ghQg/5U7YVl
iGp668u/lDlehDfGOcfa9dHLbMn56ud5nwYkaF7pT9hIf1wcZvWVnbdILLJEFWt4
fx0NeK/C5Hd0zrj8lVXNfaXMqZ/pGjwzEpKwlX1LhIVlPTjWPQjWte86fPleAJiF
7EqZy2nzvaC0aU4T8byNufMdtLRtP+Ej8uww+a/8C8NjjF+miQXjOk6AnFByhpG4
b95nq902KuxDneKRvi29MJR04Y0gQ3oo+rabNWQtvlXT9iqxcrIQP0TO2a6gLXZH
b6kRBNGkjnrfBDKtOPZ644KRODJDqDG+rkAVs2GgHf4TpMAvPQIywTDtIhADn0Sz
DLRL7zOgLqGvn7ldgs7gEWg3tXNwG4QTIOz9MrzAJHqmTfgpETyhDzORJLtivhJY
H8LLAWtYbWIWR/X6WpV57znPQ1DTDQo57ocSNwEP6X5cktyDc2eP5v9VCGChzVp3
oSbCwq91fZv+WoQA+dNI4tLKlVatcKpjjN8YfQCCgKylbDEfnDs7MIhXiDxbplDd
CONl3WT5f7qcpeABDBfB
=Zhw9
-----END PGP SIGNATURE-----
--GDUukifCTtE2ow6FsDqlqHOkICEh1iSTx--
|