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
|
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 <c1.sf-bitcoin@niftybox.net>) id 1WNQDh-00058h-NP
for bitcoin-development@lists.sourceforge.net;
Tue, 11 Mar 2014 17:12:01 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of niftybox.net
designates 95.142.167.147 as permitted sender)
client-ip=95.142.167.147;
envelope-from=c1.sf-bitcoin@niftybox.net; helo=i3.hyper.to;
Received: from i3.hyper.to ([95.142.167.147])
by sog-mx-1.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1WNQDg-0001oO-78 for bitcoin-development@lists.sourceforge.net;
Tue, 11 Mar 2014 17:12:01 +0000
Received: from localhost (localhost [127.0.0.1])
by i3.hyper.to (Postfix) with ESMTP id 160EEE03D1;
Tue, 11 Mar 2014 18:11:54 +0100 (CET)
Received: from i3.hyper.to ([127.0.0.1])
by localhost (i3.hyper.to [127.0.0.1]) (amavisd-new, port 10024)
with ESMTP id p4kA8HCPMpLc; Tue, 11 Mar 2014 18:11:53 +0100 (CET)
Received: from [127.0.0.1] (unknown [95.85.6.44])
by i3.hyper.to (Postfix) with ESMTPSA id B8995E02EA;
Tue, 11 Mar 2014 18:11:51 +0100 (CET)
Message-ID: <1394557907.9025.125.camel@mimiz>
From: Miron <c1.sf-bitcoin@niftybox.net>
To: Mike Hearn <mike@plan99.net>
Date: Tue, 11 Mar 2014 10:11:48 -0700
In-Reply-To: <CANEZrP2U_mpGSnVMr6ZBTtVPUmnKRBcEaehHXyN67WmLxLuBjw@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>
<CAJHLa0NHKWqXMd23Fr46adGinQmjcLRxyBB-Ra9tJwu4Ein7GA@mail.gmail.com>
<CAKm8k+3Eohr9OtA+tSp9nXuQpxfiAwC6R61zZWSB3WMAxCZ=Vw@mail.gmail.com>
<CANEZrP2U_mpGSnVMr6ZBTtVPUmnKRBcEaehHXyN67WmLxLuBjw@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
X-Mailer: Evolution 3.8.4-0ubuntu1
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
X-Spam-Score: -1.5 (-)
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
X-Headers-End: 1WNQDg-0001oO-78
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
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 17:12:01 -0000
On Tue, 2014-03-11 at 16:18 +0100, Mike Hearn wrote:
> You can follow HDW progress in bitcoinj on this branch:
>
>
> https://github.com/bitcoinj/bitcoinj/commits/keychain
>
>
> I've been working on it for a couple of months now. Electrum (Thomas
> V) is also making good progress, and Trezor already uses HD wallets. I
> think most popular end user wallets except blockchain.info and Bitcoin
> Core will support HDW soon enough.
Interestingly, Blockchain's android wallet is based on Android Wallet /
bitcoinj. So with HD in bitcoinj we would get Multibit, Android Wallet
(Andreas Schildbach's) and remove one roadblock to Blockchain going HD.
Electrum HD seems more or less ready. So I'm optimistic that we'll see
a pretty fast transition to HD for the majority of the user base.
HD is important for some multisig flows, including the watchdog type
where you want to detect change going back to the wallet.
>
> At any rate, as Gavin said already, the best way to make a feature you
> want happen is just to write it. Devrandom is already working on a
> watchdog service, as is another group (TrustedCoin), and that's an
> obvious use for multisig/p2sh. They have API's already, it's just a
> case of standardising them once we get more experience.
We have a proposed flow for watchdog type multisig
here:
https://cryptocorp.co/technology.htm
and a reference implementation off the Electrum 2.0 branch.
It actually works just like a regular spend from a UX point of view,
unless the watchdog decides that it needs a second factor for a risky
transaction. With a risky transaction, the user just gets a
callback or enters an OTP.
--
Miron
|
