Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 74.125.82.53 as permitted sender)
	client-ip=74.125.82.53; envelope-from=andyparkins@gmail.com;
	helo=mail-ww0-f53.google.com; 
From: Andy Parkins <andyparkins@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Date: Fri, 5 Aug 2011 12:58:25 +0100
User-Agent: KMail/1.13.6 (Linux/2.6.38-2-686; KDE/4.6.3; i686; ; )
References: <201108041423.14176.andyparkins@gmail.com>
	<4E3B35E7.1010409@justmoon.de>
	<CANEZrP1QVdOdttOk4_kzoHkVf_KYRzVFyBEpOFvi+L_DLd=74A@mail.gmail.com>
In-Reply-To: <CANEZrP1QVdOdttOk4_kzoHkVf_KYRzVFyBEpOFvi+L_DLd=74A@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="nextPart2289723.cmv5fQgnN8";
	protocol="application/pgp-signature"; micalg=pgp-sha1
Content-Transfer-Encoding: 7bit
Message-Id: <201108051258.25813.andyparkins@gmail.com>
Subject: Re: [Bitcoin-development] Double spend detection to speed up
	transaction trust
Precedence: list

--nextPart2289723.cmv5fQgnN8
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

On 2011 August 05 Friday, Mike Hearn wrote:

> How many connections "should" a node use? We faced this decision in
> BitCoinJ recently and I asked the patch writer to reduce the number.
> It seems pretty arbitrary to me - if you aren't going to relay, a
> single connection should be good enough. Yes, it makes sybil easier,
> but if you pick the one node randomly enough it might be ok?

I don't really see that "number of connections" is the relevant metric.  Fo=
r a=20
well designed bit of software the number of connections shouldn't matter. =
=20
There's a bit of overhead in the operating system per connection, but I'd b=
e=20
surprised if that ever became a limiting factor in a stateless system like=
=20
bitcoin.  In fact, bitcoin would work perfectly well as a UDP system (I'm n=
ot=20
advocating that of course), and then there would be no such thing as a=20
connection.

Bandwidth is the measure that's relevant.

Therefore if bandwidth is the measure, just pick a bandwidth you like and=20
add/accept connections until you hit that bandwidth limit (probably average=
d). =20
This has the advantage that it can be measured automatically, or sensibly s=
et=20
by a user.


Andy

=2D-=20
Dr Andy Parkins
andyparkins@gmail.com

--nextPart2289723.cmv5fQgnN8
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

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

iEYEABECAAYFAk472uEACgkQwQJ9gE9xL21G3ACgrt5J2+LEl4qh64k5rbPpLIZC
7fcAn3VL2p746sAouxB0OTIRFfnmjm5c
=3xHC
-----END PGP SIGNATURE-----

--nextPart2289723.cmv5fQgnN8--