From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Qgxxm-0003Cn-Je for bitcoin-development@lists.sourceforge.net; Wed, 13 Jul 2011 11:50:46 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.212.47 as permitted sender) client-ip=209.85.212.47; envelope-from=mh.in.england@gmail.com; helo=mail-vw0-f47.google.com; Received: from mail-vw0-f47.google.com ([209.85.212.47]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Qgxxk-0004NS-Cs for bitcoin-development@lists.sourceforge.net; Wed, 13 Jul 2011 11:50:46 +0000 Received: by vws2 with SMTP id 2so6166847vws.34 for ; Wed, 13 Jul 2011 04:50:39 -0700 (PDT) MIME-Version: 1.0 Received: by 10.52.169.71 with SMTP id ac7mr591032vdc.200.1310557838905; Wed, 13 Jul 2011 04:50:38 -0700 (PDT) Sender: mh.in.england@gmail.com Received: by 10.52.164.225 with HTTP; Wed, 13 Jul 2011 04:50:38 -0700 (PDT) In-Reply-To: <1310516279.2279.20.camel@Desktop666> References: <602127524.20110712224712@web.de> <1310516279.2279.20.camel@Desktop666> Date: Wed, 13 Jul 2011 13:50:38 +0200 X-Google-Sender-Auth: KhwW74YBk3XYmLbSvKvoNjg324k Message-ID: From: Mike Hearn To: Matt Corallo Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spam-Score: -1.5 (-) 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 (mh.in.england[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 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: 1Qgxxk-0004NS-Cs Cc: bitcoin-development@lists.sourceforge.net Subject: Re: [Bitcoin-development] overall bitcoin client code quality 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: Wed, 13 Jul 2011 11:50:46 -0000 For what it's worth,=C2=A0BitCoinJ has a NetworkParameters abstraction that does what you suggest (groups all the constants together): http://code.google.com/p/bitcoinj/source/browse/trunk/src/com/google/bitc= oin/core/NetworkParameters.java It exists primarily to make unit testing easier. In the test suite, we often build small chains and other structures. We do this by using a NetworkParameters that has the easiest difficulty possible. It means you can solve blocks in a few attempts, easily fast enough to build test chains of any length you like. I suspect that as the test suite expands, a similar abstraction will be introduced to the Satoshi client.