summaryrefslogtreecommitdiff
path: root/27/ada932f0e3629fa593dd01f3e1786824abbd2c
blob: 2f132dbabd9dffd90c6be5eaa4e577fda99f7fc6 (plain)
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
Return-Path: <hoenicke@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 8E882360
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sat, 14 May 2016 12:26:38 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-wm0-f53.google.com (mail-wm0-f53.google.com [74.125.82.53])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 0341A90
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sat, 14 May 2016 12:26:37 +0000 (UTC)
Received: by mail-wm0-f53.google.com with SMTP id g17so68002141wme.1
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sat, 14 May 2016 05:26:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=subject:to:references:from:message-id:date:user-agent:mime-version
	:in-reply-to:content-transfer-encoding;
	bh=I4aHnrb4EQtmtzm0zLBqVekVQlrOSOuaxWNZVShEj8o=;
	b=PMgH9DQhkGKnbn5Q2imntaLK8GcRHk7pe978qeT9yqP0xpt1+b3r3W9jThjiBqJkgk
	4Y8tyc3Yf6+0yaWwJ0S4pdv6I9kZEDXS3xodGr5RaI6+D/rsm4v3qmn5lG+F6WOT9Ie/
	oI9JYqLaXaCaZxYWX4E702uNhA1eW4RiPTBDfQAP9nZAPGTY6v64qR8GIxcwNaR+VfDc
	QK2YulskGwidGdWmWNdTtG6apq1BXIDG+ovibQv4nPX4jY6zSGk2bKqT7VCxj60Xcf4A
	/CkloYv0cGtmzhOWjVjEJFNJCkxZPlulIl5+JFvtfubb8eRpWsv2lRasXzXqaBrENkcQ
	aohg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20130820;
	h=x-gm-message-state:subject:to:references:from:message-id:date
	:user-agent:mime-version:in-reply-to:content-transfer-encoding;
	bh=I4aHnrb4EQtmtzm0zLBqVekVQlrOSOuaxWNZVShEj8o=;
	b=CZapK9ycvIMfwrntlFWKUL17FJTEKIdSkPE9c6ApvmLWNLNe46YbSllR2PSuQDoaTF
	yuDKxjsm782tIabSiWIN1UiiWN8O7mF+df5CO1qYyHhsWYV8z7Np4oaWGa4/XbisIpbk
	3WOzyNa5wbSY6+IQegHOx+utfCFCWzU5rFWfj5Xmv57Hv6EX5iRK4+1B5ALhqlGtE8yV
	Cyxl0+sR1RO8mQJ4I1ijKGInWy9pqzWonP9lOaRemBs8G+iZ23s7dj/DY236/rWlI0O8
	eJ9DW8mF9wEn7yzyql4/uIaniB4P+k6aCnq3Fp/kPzmcrM6ooZs6PrsAN9jEwXc6cSlt
	PpwQ==
X-Gm-Message-State: AOPr4FWG0tXxeFSuPQ0Tq2RDeBIh/wRLIM6/naG36gIj0NuvL3QBEO1hcLOFZQBD+xd/QQ==
X-Received: by 10.28.37.129 with SMTP id l123mr9162301wml.1.1463228796752;
	Sat, 14 May 2016 05:26:36 -0700 (PDT)
Received: from ?IPv6:2001:4dd0:ff00:8a0a:c68e:8fff:fef3:22ad?
	([2001:4dd0:ff00:8a0a:c68e:8fff:fef3:22ad])
	by smtp.googlemail.com with ESMTPSA id
	g197sm8137569wme.15.2016.05.14.05.26.35
	(version=TLSv1/SSLv3 cipher=OTHER);
	Sat, 14 May 2016 05:26:35 -0700 (PDT)
To: Jonas Schnelli <dev@jonasschnelli.ch>,
	Bitcoin Protocol Discussion <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>
	<5736DEEA.5030603@jonasschnelli.ch>
From: Jochen Hoenicke <hoenicke@gmail.com>
Message-ID: <5737197A.6020101@gmail.com>
Date: Sat, 14 May 2016 14:26:34 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101
	Thunderbird/38.7.2
MIME-Version: 1.0
In-Reply-To: <5736DEEA.5030603@jonasschnelli.ch>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 8bit
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID, DKIM_VALID_AU, FREEMAIL_FROM,
	RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.org
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 12:26:38 -0000

Am 14.05.2016 um 10:16 schrieb Jonas Schnelli via bitcoin-dev:
> 
> 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).

One important use case is importing xpubs for watch-only accounts. This
is necessary for hardware wallets and there are other valid use cases
for this.

> 
> 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.
>

Yes, in general it is not a good idea to import private keys and many
wallets don't even have an option to give out the xprv (except
indirectly via the backup mechanism).  But even when sweeping a
bip-44+segwit wallet you need to know where the segwit addresses are.

  Jochen