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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jgarzik@bitpay.com>) id 1WNNRg-00075K-0z
for bitcoin-development@lists.sourceforge.net;
Tue, 11 Mar 2014 14:14:16 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of bitpay.com
designates 74.125.82.181 as permitted sender)
client-ip=74.125.82.181; envelope-from=jgarzik@bitpay.com;
helo=mail-we0-f181.google.com;
Received: from mail-we0-f181.google.com ([74.125.82.181])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WNNRe-0000H4-8z
for bitcoin-development@lists.sourceforge.net;
Tue, 11 Mar 2014 14:14:16 +0000
Received: by mail-we0-f181.google.com with SMTP id q58so9933683wes.26
for <bitcoin-development@lists.sourceforge.net>;
Tue, 11 Mar 2014 07:14:08 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:mime-version:in-reply-to:references:from:date
:message-id:subject:to:cc:content-type;
bh=eCNOLAXZoscRPGfSPj4/UN77/tkI7kfDEuSqcUIfUZE=;
b=fyDitcspqP0w2L963N8UdN6BIEzzk/4Lwy2eTe0Cz7g9P1vRhlw65pvczM+KMD/O6h
B4gjMCA/wNpRrBgl36M7Pe83ID3LFv0Wx+ZY/NyIR6QG/7x2Je0GYftBi+2rpTDA19qH
Q2eLE6t69Lg5ZlO7S3LzdfCJ9Mtcpb2koZF7KiMEmsr4MwqqxwoJ+oZGupNC5UaZujMz
fflvqPv55svGZk0IqFBxRAott6rZk4SmZ/Jn2AXsbWFrruXiBBvl5xTlqnb5YykZWubL
WwCdY//2rIktGen2EV9yofZK6P+7MogYu+lxPdGttxuKnSz3eOTxU/Se/IV47QgX/Gik
I2QA==
X-Gm-Message-State: ALoCoQkx7QMc9UkY3tFJn+H6stisTNrTk42aPFwViky6O3dccCgO/jTt7eLePayX9Uiu161rMUWl
X-Received: by 10.180.87.162 with SMTP id az2mr3241768wib.23.1394547248176;
Tue, 11 Mar 2014 07:14:08 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.82.197 with HTTP; Tue, 11 Mar 2014 07:13:48 -0700 (PDT)
In-Reply-To: <CABsx9T0Lvg84qFVRbc7Ef4vZEQj9eO7Jhup5PTRLLeuJFvXi-w@mail.gmail.com>
References: <CANAnSg3Bt0e7CfUcJXe96xhU6nqif9ey_vurZMZkSa9OHjHStw@mail.gmail.com>
<CABsx9T0SMi6Gp4JY=CpHxLEu5pVkvDmnug7PsY7m_dvtT7khzg@mail.gmail.com>
<531DFDF8.80008@gmail.com> <531E52FE.5090107@jerviss.org>
<531E5454.1030601@gmail.com>
<CAJHLa0NZkzQQvMxgCJAJGT=Yn6vrVNK8Bg7RAfAjctpnrfg5zA@mail.gmail.com>
<CABsx9T3eViYDsEmLm7ceimJNwci3mCOxWoVnVZHrqp7pDmm0+g@mail.gmail.com>
<CANAnSg2kzPF0886PsQW8chzsWi6Urp+=-x+9bbv8Mv6hmpvBPw@mail.gmail.com>
<CAJHLa0Mu2kiv3CCme7BPwzWtT++PNLQ2aAKdLyA8LFTtXEg9fg@mail.gmail.com>
<CABsx9T0Lvg84qFVRbc7Ef4vZEQj9eO7Jhup5PTRLLeuJFvXi-w@mail.gmail.com>
From: Jeff Garzik <jgarzik@bitpay.com>
Date: Tue, 11 Mar 2014 10:13:48 -0400
Message-ID: <CAJHLa0Mn2_OKDH_XUXfz49hPWGdCN0gs6S3wbtc=qHkg+sJ2Xw@mail.gmail.com>
To: Gavin Andresen <gavinandresen@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
X-Spam-Score: -1.6 (-)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
-0.0 SPF_PASS SPF: sender matches SPF record
-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
author's domain
0.1 DKIM_SIGNED Message has a DKIM or DK signature,
not necessarily valid
-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1WNNRe-0000H4-8z
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>,
kjj <bitcoin-devel@jerviss.org>
Subject: Re: [Bitcoin-development] Multisign payment protocol?
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Tue, 11 Mar 2014 14:14:16 -0000
Sure, but I don't see wallets being able to _assume_ _remote_ parties
have an HD wallet for a long, long time. Interoperability common
sense implies the environment will be heterogenous, perhaps forever,
invalidating assume-each-party-uses-HD logic.
On Tue, Mar 11, 2014 at 9:51 AM, Gavin Andresen <gavinandresen@gmail.com> wrote:
> On Tue, Mar 11, 2014 at 8:38 AM, Jeff Garzik <jgarzik@bitpay.com> wrote:
>>
>> On Tue, Mar 11, 2014 at 7:43 AM, Drak <drak@zikula.org> wrote:
>> > I very much like the idea of assuming each party uses HD wallets, that
>> > certainly simplifies things greatly.
>>
>> It also assumes a reality different from our current one.
>
>
> Multisig wallets are a different reality from our current one, so when we
> move to that new reality we should do it correctly from the beginning.
>
> --
> --
> Gavin Andrese
--
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc. https://bitpay.com/
|
