blob: 459b53828764695bd4e71180353e788519b890f4 (
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
|
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <bitcoin-list@bluematt.me>) id 1Qp4gb-0005WS-PU
for bitcoin-development@lists.sourceforge.net;
Thu, 04 Aug 2011 20:38:33 +0000
Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of bluematt.me
designates 173.246.101.161 as permitted sender)
client-ip=173.246.101.161;
envelope-from=bitcoin-list@bluematt.me; helo=mail.bluematt.me;
Received: from vps.bluematt.me ([173.246.101.161] helo=mail.bluematt.me)
by sog-mx-2.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1Qp4gb-0002AL-57 for bitcoin-development@lists.sourceforge.net;
Thu, 04 Aug 2011 20:38:33 +0000
Received: from [IPv6:2001:470:9ff2:1:2c0:caff:fe33:858b] (unknown
[IPv6:2001:470:9ff2:1:2c0:caff:fe33:858b])
by mail.bluematt.me (Postfix) with ESMTPSA id 8C3ED2CCD
for <bitcoin-development@lists.sourceforge.net>;
Thu, 4 Aug 2011 22:38:20 +0200 (CEST)
From: Matt Corallo <bitcoin-list@bluematt.me>
To: bitcoin-development@lists.sourceforge.net
In-Reply-To: <82CEB610-9821-4928-8A13-30088A59223C@andrewschaaf.com>
References: <201108041423.14176.andyparkins@gmail.com>
<201108041922.16956.andyparkins@gmail.com>
<1312483196.3109.38.camel@Desktop666>
<201108042042.55214.andyparkins@gmail.com>
<82CEB610-9821-4928-8A13-30088A59223C@andrewschaaf.com>
Content-Type: multipart/signed; micalg="pgp-sha1";
protocol="application/pgp-signature";
boundary="=-X0JtjwkiycEWH0GoO0tT"
Date: Thu, 04 Aug 2011 22:38:25 +0200
Message-ID: <1312490305.3109.46.camel@Desktop666>
Mime-Version: 1.0
X-Mailer: Evolution 2.32.2
X-Spam-Score: -2.3 (--)
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.8 RP_MATCHES_RCVD Envelope sender domain matches handover relay
domain
X-Headers-End: 1Qp4gb-0002AL-57
Subject: Re: [Bitcoin-development] Double spend detection to speed up
transaction trust
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: Thu, 04 Aug 2011 20:38:33 -0000
--=-X0JtjwkiycEWH0GoO0tT
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
On Thu, 2011-08-04 at 16:07 -0400, Andrew Schaaf wrote:
> One double-spend fighting option is for each mining pool to offer a realt=
ime feed of accepted TXs.
>=20
> I am hoping to complete the following later this month:
> =09
> (1) A minimal bitcoind patch that writes raw accepted TXs and BLOCKs to =
stdout with a prefix of ("2naXaRQj--TX\n%d\n" % (data_length))
> (Proof-of-concept done =E2=80=94 I'll submit a pull request with "--pri=
nt-accepted-txs-and-blocks" when I get a chance to clean it up)
> =09
> (2) A minimal NodeJS app which invokes bitcoind as a subprocess, parses =
the TXs and BLOCKs, and offers a realtime feed
They already do if they provide the IP of their node (or a proxy node on
top of theirs which would be recommended for security). This has been
my whole point the entire time.
Matt
--=-X0JtjwkiycEWH0GoO0tT
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
iQIcBAABAgAGBQJOOwM/AAoJEBrh01BD4I5U0h4QAIIxpGb6u8n4asd0rkUGQiHv
LLhcNuAFs+s1V5Mf1lsDXalQMowAzhQ/Ma0V4Jnd6h038n+3/LiZ9qF1m/MfEPyA
CfIAZ2vJLtXbQV0Yr1WXx3+Pq8r6w1bNXZkXjlMLbUfEi1obUhz25K86m8ZiJfj0
eK35DpDmvOA5bIhXe6AoMDUruPlQgPBKwKBUzY9547PBQHA+CSf2IKhh8EvHRz8J
vgyhqwxypuIASmE0iFPPc+EK7+l7Tp8YYWlxR6IS8n/Re+gKeHxcf4KXuSL/LsAW
6zOuMRHux+v06U0CjMbxIEi2Z3T+6VppBhvmkpFYtDVE62vFUcyKKGpmPY03g+g7
f5q9Q+WPDsk7NHoUqB9w6u6DZOszV6ToHZIzDFNUQyXHWMvLEFEFWAxdHDrVsadR
RRzlva00gI5raVJOABfZpWyAOKcWzBZxsTt/dydzbLfNiNJlRgFxso1pz6Ov5VUN
1brYhIY5hvsvXumPTTS9ndaUhgKxCjEZ3KybsU87u9zfzJ0xjrO5t9WuhSHyO5xJ
JUKls0fPbHC8gGZjxrHPsoCITqDKWHblNgQVaPNSrz8WWIw/s4BBn0H/SAFFVFQw
MbbjC6BxYVPNNQMeePDNQNWueQ3PtAVWqeshbPoqtOSMtu7CXtKDso0Sn1C+OZmH
w3rnSDMM/TV9DC8wpF1a
=BzFl
-----END PGP SIGNATURE-----
--=-X0JtjwkiycEWH0GoO0tT--
|
