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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <gavinandresen@gmail.com>) id 1WNNal-0004dh-FB
for bitcoin-development@lists.sourceforge.net;
Tue, 11 Mar 2014 14:23:39 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.213.48 as permitted sender)
client-ip=209.85.213.48; envelope-from=gavinandresen@gmail.com;
helo=mail-yh0-f48.google.com;
Received: from mail-yh0-f48.google.com ([209.85.213.48])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WNNak-0000cT-O0
for bitcoin-development@lists.sourceforge.net;
Tue, 11 Mar 2014 14:23:39 +0000
Received: by mail-yh0-f48.google.com with SMTP id z6so8609092yhz.21
for <bitcoin-development@lists.sourceforge.net>;
Tue, 11 Mar 2014 07:23:33 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.236.80.8 with SMTP id j8mr1317244yhe.151.1394547812674; Tue,
11 Mar 2014 07:23:32 -0700 (PDT)
Received: by 10.170.133.195 with HTTP; Tue, 11 Mar 2014 07:23:32 -0700 (PDT)
In-Reply-To: <CAJHLa0Mn2_OKDH_XUXfz49hPWGdCN0gs6S3wbtc=qHkg+sJ2Xw@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>
Date: Tue, 11 Mar 2014 10:23:32 -0400
Message-ID: <CABsx9T3fKBCFd7d-yP-0WgN2TBwN8Es=hZqxPBnThESKz1jLvA@mail.gmail.com>
From: Gavin Andresen <gavinandresen@gmail.com>
To: Jeff Garzik <jgarzik@bitpay.com>
Content-Type: multipart/alternative; boundary=20cf300fb33dff332004f45576f9
X-Spam-Score: -0.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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(gavinandresen[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-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: 1WNNak-0000cT-O0
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:23:39 -0000
--20cf300fb33dff332004f45576f9
Content-Type: text/plain; charset=ISO-8859-1
On Tue, Mar 11, 2014 at 10:13 AM, Jeff Garzik <jgarzik@bitpay.com> wrote:
> 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.
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.
Remote parties paying into a multisig, or receiving funds from a multisig,
don't have to support it (that's what P2SH gives us).
--
--
Gavin Andresen
--20cf300fb33dff332004f45576f9
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
ue, Mar 11, 2014 at 10:13 AM, Jeff Garzik <span dir=3D"ltr"><<a href=3D"=
mailto:jgarzik@bitpay.com" target=3D"_blank">jgarzik@bitpay.com</a>></sp=
an> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">Sure, but I don't see wallets being able=
to _assume_ _remote_ parties<br>
have an HD wallet for a long, long time. =A0Interoperability common<br>
sense implies the environment will be heterogenous, perhaps forever,<br>
invalidating assume-each-party-uses-HD logic.</blockquote><div><br></div><d=
iv>If the remote party is one of the parties involved in a multisig, and sp=
eaks the "Lets set up a multisig wallet together / Lets spend from a m=
ultisig" protocols, then it should be perfectly reasonable to assume t=
hat they're HD-capable.<br>
</div><div><br></div><div>Remote parties paying into a multisig, or receivi=
ng funds from a multisig, don't have to support it (that's what P2S=
H gives us).</div><div><br></div></div>-- <br>--<br>Gavin Andresen<br>
</div></div>
--20cf300fb33dff332004f45576f9--
|
