Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of petertodd.org
	designates 62.13.148.100 as permitted sender)
	client-ip=62.13.148.100; envelope-from=pete@petertodd.org;
	helo=outmail148100.authsmtp.co.uk; 
Date: Fri, 5 Apr 2013 08:12:51 -0400
From: Peter Todd <pete@petertodd.org>
To: Melvin Carvalho <melvincarvalho@gmail.com>
Message-ID: <20130405121251.GA18254@savin>
References: <CAKaEYhLqnzrhdJNTSBccDA68Mb-hUnaZaCa9Gn43FuVpa410sg@mail.gmail.com>
	<CANEZrP3S7b+uh2LW4vH=53opopLJRmmJ-_Uad6yEQxZ3kHW47A@mail.gmail.com>
	<CAKaEYhJ9-ksVXFhnzNvWHR2QoPc72uzesvsxn7ryebvt6+zxJg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="AhhlLboLdkugWU4S"
Content-Disposition: inline
In-Reply-To: <CAKaEYhJ9-ksVXFhnzNvWHR2QoPc72uzesvsxn7ryebvt6+zxJg@mail.gmail.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] A mining pool at 46%
Precedence: list


--AhhlLboLdkugWU4S
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Apr 05, 2013 at 12:13:23PM +0200, Melvin Carvalho wrote:
> Totally see the logic of this, and it makes sense.  But I dont think the
> only risk is in terms of double spend, but rather
>=20
> 1) vandalize the block chain which may be difficult to unwind?

Vandalize the chain how? By delibrately triggering bugs? (like the old
OP_CHECKSIG abuse problem) Regardless of whether or not the
vulnerability requires multiple blocks in a row, the underlying problem
should be fixed.

By putting illegal data into it? Fundementally we have no way to prevent
people from doing that other than by making it expensive. An attacker
having a lot of hashing power just means they can do so faster and a bit
cheaper.

--=20
'peter'[:-1]@petertodd.org

--AhhlLboLdkugWU4S
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQEcBAEBAgAGBQJRXr/CAAoJEH+rEUJn5PoE1MsH/i6wLt5C1OSCWsfDK4ppVk6u
M5MIbdbwIgPB5mKrirt36i69isQ/7UlulLffU3mvG/ZoKgHZwFqu5X8Q+dKup0v/
XkoLjAazBulNo9no56KmgR20O9SpnIfJitv2W7/w7HJsrlDvQiclM+yt4NnZN7Ef
tybddiCgSd7T9sYwJBJISOH6iBB3zP/UY0jWYvnT/EiY1cGjda2kfZsmu5SEJZsG
I06GnXMrAgykpH44NUP6r3vcOzL2sqmsSn7Re3FufEeZXZZg7mYXECQtyXoOwTwq
7LZpMv+ufe/SZ1TPOlsjQy2vSRaDIJlDW9h5xVRP4VGe8KGd6BWOwb4n6vXJ3WM=
=1hMd
-----END PGP SIGNATURE-----

--AhhlLboLdkugWU4S--