From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1QpJ2z-0006vm-UB for bitcoin-development@lists.sourceforge.net; Fri, 05 Aug 2011 11:58:37 +0000 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; Received: from mail-ww0-f53.google.com ([74.125.82.53]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1QpJ2x-00021Z-J1 for bitcoin-development@lists.sourceforge.net; Fri, 05 Aug 2011 11:58:37 +0000 Received: by wwf25 with SMTP id 25so19145wwf.10 for ; Fri, 05 Aug 2011 04:58:29 -0700 (PDT) Received: by 10.216.140.141 with SMTP id e13mr1682055wej.85.1312545509397; Fri, 05 Aug 2011 04:58:29 -0700 (PDT) Received: from dvr.localnet (mail.360visiontechnology.com [92.42.121.178]) by mx.google.com with ESMTPS id a43sm1796607wed.4.2011.08.05.04.58.27 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 05 Aug 2011 04:58:28 -0700 (PDT) From: Andy Parkins 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> In-Reply-To: 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> X-Spam-Score: -1.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 (andyparkins[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -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 0.0 T_TO_NO_BRKTS_FREEMAIL To: misformatted and free email service -0.0 AWL AWL: From: address is in the auto white-list X-Headers-End: 1QpJ2x-00021Z-J1 Subject: Re: [Bitcoin-development] Double spend detection to speed up transaction trust 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: Fri, 05 Aug 2011 11:58:38 -0000 --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--