MIME-Version: 1.0
In-Reply-To: <CALqxMTGu1EtVxRYTxLBpE-0zWH59dnQa1zst9p9vdmbCckBjtQ@mail.gmail.com>
References: <CABsx9T1Bd0-aQg-9uRa4u3dGA5fKxaj8-mEkxVzX8mhdj4Gt2g@mail.gmail.com>
	<201602060012.26728.luke@dashjr.org>
	<CABm2gDrns0+eZdLyNk=tDNbnMsC1tT1MfEY93cJf1V_8TPjmLA@mail.gmail.com>
	<CABsx9T2LuMZciXpMiY24+rPzhj1VT6j=HJ5STtnQmnfnA_XFUw@mail.gmail.com>
	<CALqxMTGu1EtVxRYTxLBpE-0zWH59dnQa1zst9p9vdmbCckBjtQ@mail.gmail.com>
Date: Sat, 6 Feb 2016 12:45:14 -0500
Message-ID: <CABsx9T2AUwDdz3JowpQYeusDgCBwfNFCDz0Kfut9ffT6gSaGeQ@mail.gmail.com>
From: Gavin Andresen <gavinandresen@gmail.com>
To: Adam Back <adam@cypherspace.org>
Content-Type: multipart/alternative; boundary=001a114116bcb5d766052b1d8709
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIP proposal: Increase block size limit to 2
	megabytes
Precedence: list

--001a114116bcb5d766052b1d8709
Content-Type: text/plain; charset=UTF-8

On Sat, Feb 6, 2016 at 12:01 PM, Adam Back <adam@cypherspace.org> wrote:

>
> It would probably be a good idea to have a security considerations
> section


Containing what?  I'm not aware of any security considerations that are any
different from any other consensus rules change.

(I can write a blog post summarizing our slack discussion of SPV security
immediately after the first greater-than-1mb-block if you like).


> , also, is there a list of which exchange, library, wallet,
> pool, stats server, hardware etc you have tested this change against?
>

That testing is happening by the exchange, library, wallet, etc providers
themselves. There is a list on the Classic home page:

https://bitcoinclassic.com/


>
> Do you have a rollback plan in the event the hard-fork triggers via
> false voting as seemed to be prevalent during XT?  (Or rollback just
> as contingency if something unforseen goes wrong).
>

The only voting in this BIP is done by the miners, and that cannot be faked.

Are you talking about people spinning up pseudo-full-nodes that fake the
user-agent?

As I said, there are people who have said they will spin up thousands of
full nodes to help prevent possible Sybil attacks which would become
marginally easier to accomplish immediately after the first >1mb block was
produced and full nodes that hadn't upgraded were left behind.

Would Blockstream be willing to help out by running a dozen or two extra
full nodes?

I can't imagine any even-remotely-likely sequence of events that would
require a rollback, can you be more specific about what you are imagining?
Miners suddenly getting cold feet?


> How do you plan to monitor and manage security through the hard-fork?
>

I don't plan to monitor or manage anything; the Bitcoin network is
self-monitoring and self-managing. Services like statoshi.info will do the
monitoring, and miners and people and businesses will manage the network,
as they do every day.

-- 
--
Gavin Andresen

--001a114116bcb5d766052b1d8709
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 S=
at, Feb 6, 2016 at 12:01 PM, Adam Back <span dir=3D"ltr">&lt;<a href=3D"mai=
lto:adam@cypherspace.org" target=3D"_blank">adam@cypherspace.org</a>&gt;</s=
pan> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0p=
x 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-lef=
t-style:solid;padding-left:1ex"><br>
It would probably be a good idea to have a security considerations<br>
section</blockquote><div><br></div><div>Containing what?=C2=A0 I&#39;m not =
aware of any security considerations that are any different from any other =
consensus rules change.</div><div><br></div><div>(I can write a blog post s=
ummarizing our slack discussion of SPV security immediately after the first=
 greater-than-1mb-block if you like).</div><div><br></div><div>=C2=A0</div>=
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;p=
adding-left:1ex">, also, is there a list of which exchange, library, wallet=
,<br>
pool, stats server, hardware etc you have tested this change against?<br></=
blockquote><div><br></div><div>That testing is happening by the exchange, l=
ibrary, wallet, etc providers themselves. There is a list on the Classic ho=
me page:</div><div><br></div><div><a href=3D"https://bitcoinclassic.com/">h=
ttps://bitcoinclassic.com/</a><br></div><div>=C2=A0<br></div><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px=
;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1e=
x">
<br>
Do you have a rollback plan in the event the hard-fork triggers via<br>
false voting as seemed to be prevalent during XT?=C2=A0 (Or rollback just<b=
r>
as contingency if something unforseen goes wrong).<br></blockquote><div><br=
></div><div>The only voting in this BIP is done by the miners, and that can=
not be faked.</div><div><br></div><div>Are you talking about people spinnin=
g up pseudo-full-nodes that fake the user-agent?</div><div><br></div><div>A=
s I said, there are people who have said they will spin up thousands of ful=
l nodes to help prevent possible Sybil attacks which would become marginall=
y easier to accomplish immediately after the first &gt;1mb block was produc=
ed and full nodes that hadn&#39;t upgraded were left behind.</div><div><br>=
</div><div>Would Blockstream be willing to help out by running a dozen or t=
wo extra full nodes?</div><div><br></div><div>I can&#39;t imagine any even-=
remotely-likely sequence of events that would require a rollback, can you b=
e more specific about what you are imagining?=C2=A0 Miners suddenly getting=
 cold feet?</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(20=
4,204,204);border-left-style:solid;padding-left:1ex">How do you plan to mon=
itor and manage security through the hard-fork?<br></blockquote><div><br></=
div><div>I don&#39;t plan to monitor or manage anything; the Bitcoin networ=
k is self-monitoring and self-managing. Services like <a href=3D"http://sta=
toshi.info">statoshi.info</a> will do the monitoring, and miners and people=
 and businesses will manage the network, as they do every day.</div><div><b=
r></div></div>-- <br><div class=3D"gmail_signature"><div dir=3D"ltr"><div d=
ir=3D"ltr"><div>--<br>Gavin Andresen<br></div><div><br></div></div></div></=
div>
</div></div>

--001a114116bcb5d766052b1d8709--