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
|
Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jgarzik@bitpay.com>) id 1WNNvL-0005rz-Mv
for bitcoin-development@lists.sourceforge.net;
Tue, 11 Mar 2014 14:44:55 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of bitpay.com
designates 209.85.212.174 as permitted sender)
client-ip=209.85.212.174; envelope-from=jgarzik@bitpay.com;
helo=mail-wi0-f174.google.com;
Received: from mail-wi0-f174.google.com ([209.85.212.174])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1WNNvK-0004FO-NH
for bitcoin-development@lists.sourceforge.net;
Tue, 11 Mar 2014 14:44:55 +0000
Received: by mail-wi0-f174.google.com with SMTP id d1so992410wiv.1
for <bitcoin-development@lists.sourceforge.net>;
Tue, 11 Mar 2014 07:44:48 -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:content-type;
bh=Et0Im6UyldkfeXSGFVv4MCowxhEx9YuhAmni52cId1M=;
b=WOocR9zSvkTXKbk6Fpv+Rgbraknu0VaKs2jkjoTZ+gGWgtdzVL6gFuCcR1k6CR8rh2
g+AZOhdoSpve2IG3fhnrsGvfm20/FgkHGiDbk1ndtTb4Hsh5QMWglxU36a+de+DuYiKr
YFhXxOVzsv7rEFhEos3GGSGd884rJc3bAmHKE6WJhXQyUDkEEVb6OK1Rn63VIPn+Ubt5
HffDM4Qr9Vf5MVqAxfPxWocj47jiomIL8buon4GsbZTp+G8LIDAkmuF4keVgySN3j11o
lkb0ZynG1c9sgsati98cJV82d6p2a1qJ66fneVNiGsN4OvV4APKyZg7JdlUKmzLIXbXK
hh6Q==
X-Gm-Message-State: ALoCoQm2T2iHT+WG649Dr+hznlVmMHpeCyRaO9TwgbnUhFUIdwYfofgdZLQuSldHvxt7zMvO69Tw
X-Received: by 10.181.13.112 with SMTP id ex16mr3468806wid.23.1394549088539;
Tue, 11 Mar 2014 07:44:48 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.194.82.197 with HTTP; Tue, 11 Mar 2014 07:44:28 -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:44:28 -0400
Message-ID: <CAJHLa0NHKWqXMd23Fr46adGinQmjcLRxyBB-Ra9tJwu4Ein7GA@mail.gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
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: 1WNNvK-0004FO-NH
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:44:55 -0000
(#include <rant.h>)
Right now, HD is hot air. Let us end the pie-in-the-sky assumptions
about how HD will save the day, with zero code to back it up. Bitcoin
Wallet purportedly fails to rotate addresses, a privacy ugly, because
of this Waiting For Godot situation. An attempt to add a simple,
stateless RPC stalled because we are all Waiting For Godot, also:
https://github.com/bitcoin/bitcoin/pull/3520
Until the major user wallets and bitcoind have -basic- HD support, it
is premature to build anything on top of HD. We really have no clue
at this juncture how difficult will be the HD rollout.
--
Jeff Garzik
Bitcoin core developer and open source evangelist
BitPay, Inc. https://bitpay.com/
|
