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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jgarzik@bitpay.com>) id 1V7mQx-0002oU-KE
for bitcoin-development@lists.sourceforge.net;
Fri, 09 Aug 2013 13:08:47 +0000
Received-SPF: pass (sog-mx-2.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-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1V7mQv-0005ar-LA
for bitcoin-development@lists.sourceforge.net;
Fri, 09 Aug 2013 13:08:47 +0000
Received: by mail-wg0-f46.google.com with SMTP id k13so3519512wgh.25
for <bitcoin-development@lists.sourceforge.net>;
Fri, 09 Aug 2013 06:08:39 -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=RzY/AWS4fptt+q4NiPiE4EveK2U392Qz8gA/k/H4d2s=;
b=FSMyX7Njaz20e8SXwReR7D2Qq7lFFOFIP599yoW0aqKw0WEunjDbZAZSVlx6JZKU4E
ouppQ5v+sdo21jBYhjyPFY0DIiibLKjy+BoLmvQbOv0MwvZsXPCfW0x82URMxC/iE0Xb
c16uk6pA1QkpIEoVzF5YHWKMmF1pfmqYJCVDNvEGPFoCvzyi7Nuhoq/dnt365qdBa5Uv
TY0kdms0LoHBN6rt71a2xZD8shYbczwnBp/w2NP+m2GKIKRwoAjcsrL/PgVK5FhhAYHR
1/z4cXehVG1vB8lfNw0ez/ouXxpDXOJCEzFna0iff2YGdip5Z1tuFoaBgHJg7YyoDpTi
bGrQ==
X-Gm-Message-State: ALoCoQkf/Azg2XzsQe42ssuuxwAxNDHNBMkOxkLGKGG5QAOOIT+BITjJV6QDhI65cQ3hAFWVo98F
MIME-Version: 1.0
X-Received: by 10.194.7.137 with SMTP id j9mr6353479wja.11.1376053719476; Fri,
09 Aug 2013 06:08:39 -0700 (PDT)
Received: by 10.194.23.1 with HTTP; Fri, 9 Aug 2013 06:08:39 -0700 (PDT)
In-Reply-To: <B4D8D241-E758-4806-8B12-C9A78BF1470B@grabhive.com>
References: <B4D8D241-E758-4806-8B12-C9A78BF1470B@grabhive.com>
Date: Fri, 9 Aug 2013 09:08:39 -0400
Message-ID: <CAJHLa0NxcRHP+hoa1Drie6gfLqCJpnB17+0QsYVO6KQ7gZzYqA@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: 1V7mQv-0005ar-LA
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 13:08:48 -0000
On Fri, Aug 9, 2013 at 7:32 AM, Wendell <w@grabhive.com> wrote:
> To those of you in the know about modern browser tech:
>
> Does it seem at all conceivable that an SPV wallet could be built entirely in JavaScript? And if indeed it is within the realm of the possible, how would such a thing be safely distributed for use? Would a signed Chrome Plugin be an ideal vehicle?
Certainly. BitPay is working on such a wallet:
https://github.com/jgarzik/wally
wally uses node.js JavaScript, and not browser JavaScript, so not
exactly what you're talking about...
--
Jeff Garzik
Senior Software Engineer and open source evangelist
BitPay, Inc. https://bitpay.com/
|
