From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Wj561-0001VO-9K for Bitcoin-development@lists.sourceforge.net; Sat, 10 May 2014 11:05:37 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 74.125.82.181 as permitted sender) client-ip=74.125.82.181; envelope-from=ewillbefull@gmail.com; helo=mail-we0-f181.google.com; Received: from mail-we0-f181.google.com ([74.125.82.181]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Wj55z-0001tg-MJ for Bitcoin-development@lists.sourceforge.net; Sat, 10 May 2014 11:05:37 +0000 Received: by mail-we0-f181.google.com with SMTP id w61so5027186wes.12 for ; Sat, 10 May 2014 04:05:29 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.180.92.69 with SMTP id ck5mr7373915wib.15.1399719929308; Sat, 10 May 2014 04:05:29 -0700 (PDT) Received: by 10.194.10.40 with HTTP; Sat, 10 May 2014 04:05:29 -0700 (PDT) In-Reply-To: <5279D49D.5050807@jerviss.org> References: <5279D49D.5050807@jerviss.org> Date: Sat, 10 May 2014 05:05:29 -0600 Message-ID: From: E willbefull To: kjj Content-Type: multipart/alternative; boundary=20cf306847392beaee04f909b1e4 X-Spam-Score: -0.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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (ewillbefull[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: 1Wj55z-0001tg-MJ Cc: Bitcoin-development@lists.sourceforge.net 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 10 May 2014 11:05:37 -0000 --20cf306847392beaee04f909b1e4 Content-Type: text/plain; charset=UTF-8 I've created a simulation framework called simbit to simulate the selfish mining attack, though it is general enough to simulate any p2p network. I even put together a rough simulation of MinCen. The goal is to be fun/easy to rapidly prototype protocols and strategies, and visualize them. It's written in javascript, so it can be demoed in the web browser or run on Node. It's still in early alpha and a lot of things are missing. https://github.com/ebfull/simbit https://bitcointalk.org/index.php?topic=603171.0 Feedback is appreciated! On Tue, Nov 5, 2013 at 10:33 PM, kjj wrote: > One of the things that really gets me going is when someone devises a > model, tests it against itself, and then pretends that they've learned > something about the real world. > > Naturally, the Selfish Mining paper is exactly this sort of nonsense. > Their model is one with no latency, and one where the attacker has total > visibility across the network. An iterated FSM is not a suitable > simulation of the bitcoin system. The bitcoin network does not have > states, and to the extent that you can pretend that we do, you can't > simulate transitions between them with static probabilities. > > The authors understand this deep down inside, even though they didn't > work out the implications. They handwave the issue by assuming a total > sybil attack, and in true academic spirit, they don't realize that the > condition necessary for the attack is far, far worse than the attack > itself. > > Greg said he'd like to run some simulations, and I'm thinking about it > too. Unfortunately, he is busy all week, and I'm lazy (and also busy > for most of tomorrow). > > If neither of us get to it first, I'm willing to pitch in 1 BTC as a > bounty for building a general bitcoin network simulator framework. The > simulator should be able to account for latency between nodes, and > ideally within a node. It needs to be able to simulate an attacker that > owns varying fractions of the network, and make decisions based only on > what the attacker actually knows. It needs to be able to simulate this > "attack" and should be generic enough to be easily modified for other > crazy schemes. > > (Bounty offer is serious, but expires in one year [based on the earliest > timestamp that my mail server puts on this email], and /may/ be subject > to change if the price on any reputable exchange breaks 1000 USD per BTC > in that period.) > > Basically, the lack of a decent network simulator is what allowed this > paper to get press. If the author had been able to see the importance > of the stuff he was ignoring, we wouldn't be wasting so much time > correcting him (and sadly the reporters that have no way to check his > claims). > > https://bitcointalk.org/index.php?topic=324413.msg3495663#msg3495663 > > > > > ------------------------------------------------------------------------------ > 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 > --20cf306847392beaee04f909b1e4 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I've created a simulation framework called s= imbit to simulate the selfish mining attack, though it is general enough to= simulate any p2p network. I even put together a rough simulation of MinCen= . The goal is to be fun/easy to rapidly prototype protocols and strategies,= and visualize them. It's written in javascript, so it can be demoed in= the web browser or run on Node.

It's still in early alpha and a lot of things are missin= g.
Feedback is appreciated!


On Tue, Nov 5, 2013 at 10:33 PM, kjj <= span dir=3D"ltr"><bitcoin-devel@jerviss.org> wrote:
One of the things that really gets me going = is when someone devises a
model, tests it against itself, and then pretends that they've learned<= br> something about the real world.

Naturally, the Selfish Mining paper is exactly this sort of nonsense.
Their model is one with no latency, and one where the attacker has total visibility across the network. =C2=A0An iterated FSM is not a suitable
simulation of the bitcoin system. =C2=A0The bitcoin network does not have states, and to the extent that you can pretend that we do, you can't simulate transitions between them with static probabilities.

The authors understand this deep down inside, even though they didn't work out the implications. =C2=A0They handwave the issue by assuming a tota= l
sybil attack, and in true academic spirit, they don't realize that the<= br> condition necessary for the attack is far, far worse than the attack itself= .

Greg said he'd like to run some simulations, and I'm thinking about= it
too. =C2=A0Unfortunately, he is busy all week, and I'm lazy (and also b= usy
for most of tomorrow).

If neither of us get to it first, I'm willing to pitch in 1 BTC as a bounty for building a general bitcoin network simulator framework. The
simulator should be able to account for latency between nodes, and
ideally within a node. =C2=A0It needs to be able to simulate an attacker th= at
owns varying fractions of the network, and make decisions based only on
what the attacker actually knows. =C2=A0It needs to be able to simulate thi= s
"attack" and should be generic enough to be easily modified for o= ther
crazy schemes.

(Bounty offer is serious, but expires in one year [based on the earliest timestamp that my mail server puts on this email], and /may/ be subject
to change if the price on any reputable exchange breaks 1000 USD per BTC in that period.)

Basically, the lack of a decent network simulator is what allowed this
paper to get press. =C2=A0If the author had been able to see the importance=
of the stuff he was ignoring, we wouldn't be wasting so much time
correcting him (and sadly the reporters that have no way to check his
claims).

https://bitcointalk.org/index.php?topic=3D324413.= msg3495663#msg3495663



---------------------------------------------------------------------------= ---
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explor= e
techniques for threading, error checking, porting, and tuning. Get the most=
from the latest Intel processors and coprocessors. See abstracts and regist= er
http://pubads.g.doubleclick.net/gam= pad/clk?id=3D60136231&iu=3D/4140/ostg.clktrk
_______________________________________________
Bitcoin-development mailing list
Bitcoin-develo= pment@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-de= velopment

--20cf306847392beaee04f909b1e4--