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
|
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 1V7r7z-0004Nf-EC
for bitcoin-development@lists.sourceforge.net;
Fri, 09 Aug 2013 18:09:31 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of bitpay.com
designates 209.85.212.170 as permitted sender)
client-ip=209.85.212.170; envelope-from=jgarzik@bitpay.com;
helo=mail-wi0-f170.google.com;
Received: from mail-wi0-f170.google.com ([209.85.212.170])
by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1V7r7x-0004D0-KZ
for bitcoin-development@lists.sourceforge.net;
Fri, 09 Aug 2013 18:09:31 +0000
Received: by mail-wi0-f170.google.com with SMTP id hi8so24978wib.3
for <bitcoin-development@lists.sourceforge.net>;
Fri, 09 Aug 2013 11:09:23 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=google.com; s=20120113;
h=x-gm-message-state:mime-version:in-reply-to:references:date
:message-id:subject:from:to:cc:content-type;
bh=XY2jR3H86hGnRP90i80ZhU/7BUxnoQjvHeIN5WWKQ1Y=;
b=ML/Oe2jLgQYSAV3O2ejqdSOC871EdgZZGcJ831vi0eaoZvyAr+9yxkjLUUfI45qBsy
wYtUrk5wJzbQ+1Gau9aE4HSe6GOK+y5K92cbvRGubXFeQUhNcwB4m3tMTb+Jda6sVw1l
Q2qj87kj+fcQ5pf2QaaJ/viFXVom9fNpA+yMJ8NzVc6+LUBv8I/nskUbXsFQcN9rVcRG
kriWvb7XeZLmsCfpM0VP0Mp1V3jsgHId82eKcrH869wa3X+NYUdIhJvIQpjeaf1IfxO0
aCcPRAr2ls7Hk2mPYXs2eLszZ6BjlAe065MssfacTMf5iNgHTPgZgI7eVEKXhjMvHwhC
DpDg==
X-Gm-Message-State: ALoCoQmaJqnEcDpcwtucdoZDt3Djgh9xRr2oGSaCbRGb9d1u6sI7wmoqmBaAFbhtAimXrpYK8Nq5
MIME-Version: 1.0
X-Received: by 10.180.198.79 with SMTP id ja15mr924364wic.36.1376071763120;
Fri, 09 Aug 2013 11:09:23 -0700 (PDT)
Received: by 10.194.23.1 with HTTP; Fri, 9 Aug 2013 11:09:23 -0700 (PDT)
In-Reply-To: <703284F8-88EE-4CF1-A78C-CE0DBC88A16F@grabhive.com>
References: <B4D8D241-E758-4806-8B12-C9A78BF1470B@grabhive.com>
<CAJHLa0NxcRHP+hoa1Drie6gfLqCJpnB17+0QsYVO6KQ7gZzYqA@mail.gmail.com>
<703284F8-88EE-4CF1-A78C-CE0DBC88A16F@grabhive.com>
Date: Fri, 9 Aug 2013 14:09:23 -0400
Message-ID: <CAJHLa0NGEUkVh=OyrbmvvGgaT8KkQjzPp54Nof0D74N2Epuw5g@mail.gmail.com>
From: Jeff Garzik <jgarzik@bitpay.com>
To: Wendell <w@grabhive.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: 1V7r7x-0004D0-KZ
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] SPV client in pure JavaScript?
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: Fri, 09 Aug 2013 18:09:31 -0000
On Fri, Aug 9, 2013 at 1:58 PM, Wendell <w@grabhive.com> wrote:
> No, it's not -- but that's certainly very cool to see Jeff.
>
> How is BitPay going to put this to use?
Well, "wally" is just a demo application, a command line client to
prove a technology.
The main development is in places like "node-libcoin", where a wallet
platform is being developed. While maintaining a strong commitment to
the blockchain engine side of bitcoind, BitPay has enterprise wallet
needs that do not necessarily mesh well with the standard bitcoind
wallet. Multi-sig, P2SH and other advanced features are key to the
future use of bitcoin in large enterprises. Managers, CEOs and other
functionaries at a corporation may each have their own wallets /
keyrings, and cooperate to sign large value, high security bitcoin
multi-sig transactions, for example.
--
Jeff Garzik
Senior Software Engineer and open source evangelist
BitPay, Inc. https://bitpay.com/
|
