Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from <gavinandresen@gmail.com>) id 1Wapn4-0001CE-0R for bitcoin-development@lists.sourceforge.net; Thu, 17 Apr 2014 17:07:58 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.160.177 as permitted sender) client-ip=209.85.160.177; envelope-from=gavinandresen@gmail.com; helo=mail-yk0-f177.google.com; Received: from mail-yk0-f177.google.com ([209.85.160.177]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Wapn0-0000MX-7a for bitcoin-development@lists.sourceforge.net; Thu, 17 Apr 2014 17:07:57 +0000 Received: by mail-yk0-f177.google.com with SMTP id q200so560544ykb.8 for <bitcoin-development@lists.sourceforge.net>; Thu, 17 Apr 2014 10:07:48 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.236.84.227 with SMTP id s63mr24260137yhe.26.1397754468754; Thu, 17 Apr 2014 10:07:48 -0700 (PDT) Received: by 10.170.133.140 with HTTP; Thu, 17 Apr 2014 10:07:48 -0700 (PDT) In-Reply-To: <CAC1+kJMxjNReSMxm=vDB-iYyXTqBvXq5_aw0Z3onds0zF-Oq=w@mail.gmail.com> References: <CAC1+kJMrpx0tyE8d0wkwjBthhSPMCdr=9LrJHQFTF4G1vg4MAg@mail.gmail.com> <CABsx9T1HGwozy8pY+iStGZPmjenu0RQBVdtOy5ibiWG0BM4mZw@mail.gmail.com> <CAC1+kJPvzxsSDg3joraZbv_r1RroK9d6-v9O_15g6S7B46TwQg@mail.gmail.com> <CANEZrP3s9SpBWxLYMvF5cLK4UeKS2SdKOLpNr40NKGoAzh=3nw@mail.gmail.com> <CAC1+kJMxjNReSMxm=vDB-iYyXTqBvXq5_aw0Z3onds0zF-Oq=w@mail.gmail.com> Date: Thu, 17 Apr 2014 13:07:48 -0400 Message-ID: <CABsx9T23Upk+eAaHa_dPa1hQEZO1RPRMv7HfiLzbSrR14Z+NSg@mail.gmail.com> From: Gavin Andresen <gavinandresen@gmail.com> To: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= <jtimon@monetize.io> Content-Type: multipart/alternative; boundary=20cf3011dd8597e92e04f7401245 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 (gavinandresen[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: 1Wapn0-0000MX-7a Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net> Subject: Re: [Bitcoin-development] Timed testing 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, 17 Apr 2014 17:07:58 -0000 --20cf3011dd8597e92e04f7401245 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable On Thu, Apr 17, 2014 at 12:09 PM, Jorge Tim=C3=B3n <jtimon@monetize.io> wro= te: > So it seems a new mode only makes sense if the -private mode makes > sense, which in turn only makes sense to include in bitcoind if it's > useful enough for the network attack simulations, which remains the > open question. > Unless I misunderstood what your private mode does, you can get the same effect with -regtest by just controlling nodes connectivity. For example: Start 2 nodes, connected to each other. Mine a -regtest chain they both agree on. Restart them so they're not connected. Have one mine normally, have the other mine... however you like to simulate some attack (deep chain re-org, double-spend, whatever). To simulate launching the attack, connect them together again, let the two chains compete and see what happens. --=20 -- Gavin Andresen --20cf3011dd8597e92e04f7401245 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T= hu, Apr 17, 2014 at 12:09 PM, Jorge Tim=C3=B3n <span dir=3D"ltr"><<a hre= f=3D"mailto:jtimon@monetize.io" target=3D"_blank">jtimon@monetize.io</a>>= ;</span> wrote:<br> <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p= x #ccc solid;padding-left:1ex"><div class=3D"HOEnZb"><div class=3D"h5"><spa= n style=3D"color:rgb(34,34,34)">So it seems a new mode only makes sense if = the -private mode makes</span><br> </div></div> sense, which in turn only makes sense to include in bitcoind if it's<br= > useful enough for the network attack simulations, which remains the<br> open question.<br> </blockquote></div><br>Unless I misunderstood what your private mode does, = you can get the same</div><div class=3D"gmail_extra">effect with -regtest b= y just controlling nodes connectivity. For example:</div><div class=3D"gmai= l_extra"> <br></div><div class=3D"gmail_extra">Start 2 nodes, connected to each other= . Mine a -regtest chain they both agree on.</div><div class=3D"gmail_extra"= ><br></div><div class=3D"gmail_extra">Restart them so they're not conne= cted. =C2=A0Have one mine normally,</div> <div class=3D"gmail_extra">have the other =C2=A0mine... however you like to= simulate some attack (deep chain re-org, double-spend,</div><div class=3D"= gmail_extra">whatever).</div><div class=3D"gmail_extra"><div><br></div><div= >To simulate launching the attack, connect them together again, let the two= chains compete and see</div> <div>what happens.</div><div><br></div><div>--=C2=A0<br></div>--<br>Gavin A= ndresen<br> </div></div> --20cf3011dd8597e92e04f7401245--