blob: 7c114b89a6169ad71725c84b786114f37b9c6ddf (
plain)
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
|
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 <wendel@314t.com>) id 1V7kwc-0006Uz-Al
for bitcoin-development@lists.sourceforge.net;
Fri, 09 Aug 2013 11:33:22 +0000
X-ACL-Warn:
Received: from mail-ea0-f170.google.com ([209.85.215.170])
by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1V7kwX-0000jk-Gl
for bitcoin-development@lists.sourceforge.net;
Fri, 09 Aug 2013 11:33:22 +0000
Received: by mail-ea0-f170.google.com with SMTP id h14so1997594eak.29
for <bitcoin-development@lists.sourceforge.net>;
Fri, 09 Aug 2013 04:33:11 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=google.com; s=20120113;
h=x-gm-message-state:sender:from:content-type:subject:date:message-id
:to:mime-version;
bh=4aW5N8g/grDUt9nNjUaOWZ1ki6oSAZcLEYSln+gnI1E=;
b=iIBmJ+Hh9eJHtrhVVtFmzig9K3dH1QWTCqMIEqvoH8ssWxKYIQqZ+jUkRNAbWjTz4/
yuPWbRQBRAz0AS9Ag6UbhsHUL17Jjo5N8QfkkxQkaBcX59OJHDqoLWNn0GZs/Lm4p8k7
hm6KLFiIocZ/Lfg+nY+zxoRaG3AieqThhMtVk26yHSPbgpkcRwNQ/Zeiyq/S4eM/U30f
R67PsTOOpVgHU34lTNMf9FCPxN/534OGIK2Hb6+LW8IsUNksNVOOLYBn8mbOoNxMBFvi
lZQckttms8YqTynd45KakrySPu52lS9+xmBvY58YqdunvxwYju934pXVuvSm7NvRYgOO
v0PQ==
X-Gm-Message-State: ALoCoQkdR6Uu93/0YgYV8Gh+PSnvbugGXkur905J/OxTGGhGQwog5ClOZx5N6PBhWv4yIJnnAGex
X-Received: by 10.15.26.199 with SMTP id n47mr185662eeu.88.1376047990708;
Fri, 09 Aug 2013 04:33:10 -0700 (PDT)
Received: from [127.0.0.1] ([82.221.102.245]) by mx.google.com with ESMTPSA id
n42sm27886469eeh.15.2013.08.09.04.33.06
for <bitcoin-development@lists.sourceforge.net>
(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
Fri, 09 Aug 2013 04:33:09 -0700 (PDT)
Sender: w grabhive <wendel@314t.com>
From: Wendell <w@grabhive.com>
Content-Type: multipart/signed;
boundary="Apple-Mail=_D8F3B036-0B18-4D56-B5B7-0D5C7C732593";
protocol="application/pgp-signature"; micalg=pgp-sha1
Date: Fri, 9 Aug 2013 13:32:31 +0200
Message-Id: <B4D8D241-E758-4806-8B12-C9A78BF1470B@grabhive.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Mime-Version: 1.0 (Apple Message framework v1283)
X-Mailer: Apple Mail (2.1283)
X-Spam-Score: 1.9 (+)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
0.6 RCVD_IN_SORBS_WEB RBL: SORBS: sender is an abusable web server
[82.221.102.245 listed in dnsbl.sorbs.net]
1.2 RCVD_IN_BL_SPAMCOP_NET RBL: Received via a relay in bl.spamcop.net
[Blocked - see <http://www.spamcop.net/bl.shtml?82.221.102.245>]
X-Headers-End: 1V7kwX-0000jk-Gl
Subject: [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 11:33:22 -0000
--Apple-Mail=_D8F3B036-0B18-4D56-B5B7-0D5C7C732593
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=us-ascii
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?
-wendell
grabhive.com | twitter.com/grabhive | gpg: 6C0C9411
--Apple-Mail=_D8F3B036-0B18-4D56-B5B7-0D5C7C732593
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
filename=signature.asc
Content-Type: application/pgp-signature;
name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.18 (Darwin)
iQIcBAEBAgAGBQJSBNNQAAoJECAN2ykHU5Y6irIP/0SJJ/F1jHJgxWF7PMTF18UG
tWaDKFHyUfmZR9bd6PnoBYPTQNkJAuWyi1qVSuNlYP7tumHGSAopg9BBRkkKsGuR
5ywIfE4nOA/7+IfX3VUrtCOXRD6F+QOBb8UObGOdRG3/l9ajhFxx8wzPB8umMIlV
6fEq4cg/1g+O8pQUk8ftVhJiQrB1/5amRb0jME6RmZF8TpGQ+WcORQbq/xY3eWws
ynWDFV0duZk9AGyRTm3nCkky76gajJuf16FkbZw7sO9iAtInyDEXfn4mRCl4E2em
730AjGEd/zzpTM2wWUDOo+qWu62zbSMV2Y7Fp2IFVKWKZW2aDE2Q5DZ6ET1hWCZ7
Txbffo8I+vGas8PkygI5RgMpztfJTRA0j+jWLU/2dbd5Ry7MZtFFS1aXPROGjQu4
LbuTZjDqXM/AYzSKtDbaQefkuorgG1Tw9YZGFMqDP0v595Hmc9N/j0xi/3mBSInK
FrfMVXVntnrs2trBbOAAgn5ycOUWsTXofurfBEkJJ/5LUeccdATu4JKad9Ik6e1T
kHr6zNAVyESngkiP8g4e/zP486EgsaJWeGHV4LrWtT0Gx+zyG9IgrM2mRhf3rka0
Cs4PeZZLsUFQA1F7OuQ/yhkeSUe1sA915YkOvPukD23p65Rs3LEdO2HD3S3tX05a
QOpoWc0o8LaPX7jVuwwE
=GJgl
-----END PGP SIGNATURE-----
--Apple-Mail=_D8F3B036-0B18-4D56-B5B7-0D5C7C732593--
|
