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
|
Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jgarzik@bitpay.com>) id 1WNNm1-0006vZ-CD
for bitcoin-development@lists.sourceforge.net;
Tue, 11 Mar 2014 14:35:17 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of bitpay.com
designates 74.125.82.46 as permitted sender)
client-ip=74.125.82.46; envelope-from=jgarzik@bitpay.com;
helo=mail-wg0-f46.google.com;
Received: from mail-wg0-f46.google.com ([74.125.82.46])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WNNm0-0004Ck-EU
for bitcoin-development@lists.sourceforge.net;
Tue, 11 Mar 2014 14:35:17 +0000
Received: by mail-wg0-f46.google.com with SMTP id b13so4059405wgh.29
for <bitcoin-development@lists.sourceforge.net>;
Tue, 11 Mar 2014 07:35:10 -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=QxI/uq7MJSMlW3Py6IAs4zKbCTb0/mTH44mxTLECgiw=;
b=Kbeap4OH4v8JxeyYCJukyUey87E4qAjVfmj5cFCaxFyFZW/3zIRxw4Cdy3+5ST8mEq
1HsfEF+ZXqRNmUKz3fDGopieufBt9WcDpDVv0oVB9z7BWfsPSAtdhhlrPnPSpwDgZNeU
0M9nXcSCI9qtzgWTHjpDZXMk1mumOZZrUBdATp45RmT/OlnAVvIt1tPRXw9C/B6uWRHp
xL95yJK8ToWv5bGijGGTdYBIC3cK+z+g61yf11J+1Bu9xK39HvTFByh933vPu2LxFNQd
Jcdt1gjS1GVqb7WiyQCrQ9B1mchMLNy0TeQpo6+MJkxnjT/flDOMs9nnt4WBw3uwanHt
+bQw==
X-Gm-Message-State: ALoCoQkFL9/jzjTgdo3+yV3OiJVep7MrOmlgyy42vlu5cbWDN4kXe35MZBfBLbkkzT0V/tap7YSt
X-Received: by 10.180.149.143 with SMTP id ua15mr3241968wib.36.1394548510213;
Tue, 11 Mar 2014 07:35:10 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.82.197 with HTTP; Tue, 11 Mar 2014 07:34:50 -0700 (PDT)
In-Reply-To: <CABsx9T3fKBCFd7d-yP-0WgN2TBwN8Es=hZqxPBnThESKz1jLvA@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>
<CAJHLa0Mn2_OKDH_XUXfz49hPWGdCN0gs6S3wbtc=qHkg+sJ2Xw@mail.gmail.com>
<CABsx9T3fKBCFd7d-yP-0WgN2TBwN8Es=hZqxPBnThESKz1jLvA@mail.gmail.com>
From: Jeff Garzik <jgarzik@bitpay.com>
Date: Tue, 11 Mar 2014 10:34:50 -0400
Message-ID: <CAJHLa0NsD1cHNMqLT2vjbu_4NDES5RjqNraCvPW0bp6Kc=7FhQ@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: 1WNNm0-0004Ck-EU
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:35:17 -0000
On Tue, Mar 11, 2014 at 10:23 AM, Gavin Andresen
<gavinandresen@gmail.com> wrote:
> If the remote party is one of the parties involved in a multisig, and speaks
> the "Lets set up a multisig wallet together / Lets spend from a multisig"
> protocols, then it should be perfectly reasonable to assume that they're
> HD-capable.
Disagree. It is an unnecessary restriction. People are already
writing and starting to deploy multisig wallets in the field, that do
not match this assumption.
In general, HD is really cool, but even the barest amount of
infrastructure is lacking. Popular libraries and the reference client
all lack support. Building a protocol that assumes HD is optimistic
at this stage.
--
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc. https://bitpay.com/
|
