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
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <christophe.biocca@gmail.com>) id 1Ve7VG-00080c-NG
for Bitcoin-development@lists.sourceforge.net;
Wed, 06 Nov 2013 18:06:54 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.220.45 as permitted sender)
client-ip=209.85.220.45;
envelope-from=christophe.biocca@gmail.com;
helo=mail-pa0-f45.google.com;
Received: from mail-pa0-f45.google.com ([209.85.220.45])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Ve7VF-0006qX-OD
for Bitcoin-development@lists.sourceforge.net;
Wed, 06 Nov 2013 18:06:54 +0000
Received: by mail-pa0-f45.google.com with SMTP id kp14so9560pab.32
for <Bitcoin-development@lists.sourceforge.net>;
Wed, 06 Nov 2013 10:06:47 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.66.129.141 with SMTP id nw13mr5222054pab.167.1383761207600;
Wed, 06 Nov 2013 10:06:47 -0800 (PST)
Received: by 10.68.146.72 with HTTP; Wed, 6 Nov 2013 10:06:47 -0800 (PST)
In-Reply-To: <CAJHLa0N1-8LfFuWq=vS0r-t2Bt-qZ6yKuGjrnicUOj+K6Gpx5A@mail.gmail.com>
References: <5279D49D.5050807@jerviss.org>
<CAJHLa0N1-8LfFuWq=vS0r-t2Bt-qZ6yKuGjrnicUOj+K6Gpx5A@mail.gmail.com>
Date: Wed, 6 Nov 2013 13:06:47 -0500
Message-ID: <CANOOu=-MsPPgACKcHvsvtFAOAiULL+BOQvJz1tC3L=nT8wN01Q@mail.gmail.com>
From: Christophe Biocca <christophe.biocca@gmail.com>
To: Bitcoin-development@lists.sourceforge.net
Content-Type: multipart/alternative; boundary=001a11364fb63babdb04ea860341
X-Spam-Score: -0.6 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked.
See
http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
for more information. [URIs: doubleclick.net]
-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
sender-domain
0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
(christophe.biocca[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
-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: 1Ve7VF-0006qX-OD
Subject: Re: [Bitcoin-development] we can all relax now
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: Wed, 06 Nov 2013 18:06:54 -0000
--001a11364fb63babdb04ea860341
Content-Type: text/plain; charset=ISO-8859-1
I might try building this sometime soon. I think it may also serve an
educational purpose when trying to understand the whole network's behaviour.
What level of accuracy are we looking for though? Obviously we need to
fully emulate the steps of the network protocol, and we need to be able to
specify time taken for transmission/processing for each node. Do we care
about the actual contents of the messages (to be able to simulate double
spend attempts, invalid transactions and blocks, SPV node communication),
and their validation (actual signatures and proof of work)?
I imagine the latter is pretty useless, beyond specifying that the
signature/proof of work is valid/invalid.
If we could build up a set of experiments we'd like to run on it, it would
help clarify what's needed.
Off the top of my head:
- Peter Todd's miner strategy of sending blocks to only 51% of the
hashpower.
- Various network split conditions, and how aware of the split nodes would
be (and the effect of client variability).
- Testing the feasability of network race double spends, or Finney attacks.
- Various network partition scenarios.
- Tricking SPV nodes.
On Nov 6, 2013 6:37 AM, "Jeff Garzik" <jgarzik@bitpay.com> wrote:
> I will contribute 1 BTC to this bounty, under same terms and expiration.
>
>
> ------------------------------------------------------------------------------
> November Webinars for C, C++, Fortran Developers
> Accelerate application performance with scalable programming models.
> Explore
> techniques for threading, error checking, porting, and tuning. Get the most
> from the latest Intel processors and coprocessors. See abstracts and
> register
> http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
--001a11364fb63babdb04ea860341
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><p>I might try building this sometime soon. I think it may=
also serve an educational purpose when trying to understand the whole netw=
ork's behaviour.</p><p>What level of accuracy are we looking for though=
? Obviously we need to fully emulate the steps of the network protocol, and=
we need to be able to specify time taken for transmission/processing for e=
ach node. Do we care about the actual contents of the messages (to be able =
to simulate double spend attempts, invalid transactions and blocks, SPV nod=
e communication), and their validation (actual signatures and proof of work=
)?<br>
</p><p>I imagine the latter is pretty useless, beyond specifying that the s=
ignature/proof of work is valid/invalid.</p><p>If we could build up a set o=
f experiments we'd like to run on it, it would help clarify what's =
needed.</p>
<p>Off the top of my head:</p><p>- Peter Todd's miner strategy of sendi=
ng blocks to only 51% of the hashpower.<br>- Various network split conditio=
ns, and how aware of the split nodes would be (and the effect of client var=
iability).<br>
- Testing the feasability of network race double spends, or Finney attacks.=
<br>- Various network partition scenarios.<br>- Tricking SPV nodes.<br></p>=
<div class=3D"gmail_quote">On Nov 6, 2013 6:37 AM, "Jeff Garzik" =
<<a href=3D"mailto:jgarzik@bitpay.com" target=3D"_blank">jgarzik@bitpay.=
com</a>> wrote:<br type=3D"attribution">
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<p>I will contribute 1 BTC to this bounty, under same terms and expiration.=
</p>
<br>-----------------------------------------------------------------------=
-------<br>
November Webinars for C, C++, Fortran Developers<br>
Accelerate application performance with scalable programming models. Explor=
e<br>
techniques for threading, error checking, porting, and tuning. Get the most=
<br>
from the latest Intel processors and coprocessors. See abstracts and regist=
er<br>
<a href=3D"http://pubads.g.doubleclick.net/gampad/clk?id=3D60136231&iu=
=3D/4140/ostg.clktrk" target=3D"_blank">http://pubads.g.doubleclick.net/gam=
pad/clk?id=3D60136231&iu=3D/4140/ostg.clktrk</a><br>___________________=
____________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net" target=3D"_bla=
nk">Bitcoin-development@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
<br></blockquote></div>
</div>
--001a11364fb63babdb04ea860341--
|
