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 1RrVsM-0006sf-Pg for bitcoin-development@lists.sourceforge.net; Sun, 29 Jan 2012 14:37:02 +0000 X-ACL-Warn: Received: from nm36-vm1.bullet.mail.ne1.yahoo.com ([98.138.229.113]) by sog-mx-2.v43.ch3.sourceforge.com with smtp (Exim 4.76) id 1RrVsL-00043D-MH for bitcoin-development@lists.sourceforge.net; Sun, 29 Jan 2012 14:37:02 +0000 Received: from [98.138.90.50] by nm36.bullet.mail.ne1.yahoo.com with NNFMP; 29 Jan 2012 14:36:55 -0000 Received: from [98.138.87.9] by tm3.bullet.mail.ne1.yahoo.com with NNFMP; 29 Jan 2012 14:36:55 -0000 Received: from [127.0.0.1] by omp1009.mail.ne1.yahoo.com with NNFMP; 29 Jan 2012 14:36:55 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 911213.77034.bm@omp1009.mail.ne1.yahoo.com Received: (qmail 48866 invoked by uid 60001); 29 Jan 2012 14:36:55 -0000 X-YMail-OSG: X1CMDz4VM1nTGwpAEpYPJuRwbh5oNAy.AKhwt24IOFlGfte PC1bC4na81lnwe.PxYjWi8gfff24AADFmB03clmVrZySneIDek.GhgM3UmOX QRafp9ER0J5nMJJL.YnLr7gzB5r7I1JzvQ0wOA82BYDtjfCL_cwqyNEzgukl TAwiL3cUZZyQX9yNFSFhKk4fpEWRofJ1ThkX5GdvkstzuqLdZ.kkClRFmhHd bPbm8E6wAG6EjUglD1JcJQlGiWjzvh0B07gDliwmY4_tXUsdt7SnoYsEWR.3 JAc6MHKVnU0Fnw1seH4Gt0MW0CW1vGOCxmXKhSFm5lwfuW2RCpFGBciaBEXv hyzTMlum7JmI0Xcbitc3gXp5Lo.Xmshg4V8uavDi5II._94wR_KpzS9L5trN Ftw0jVjATUgj0.IaJHKN1eRdmCgeOsmUbYLTXge59QPjwfIt7IBLBDOA2qqJ vtuL39t2tsnF1LyZG0iJ7kbLtszmZ Received: from [92.20.138.208] by web121004.mail.ne1.yahoo.com via HTTP; Sun, 29 Jan 2012 06:36:55 PST X-Mailer: YahooMailWebService/0.8.116.331537 Message-ID: <1327847815.40132.YahooMailNeo@web121004.mail.ne1.yahoo.com> Date: Sun, 29 Jan 2012 06:36:55 -0800 (PST) From: Amir Taaki To: "bitcoin-development@lists.sourceforge.net" MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Spam-Score: 0.1 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (zgenjix[at]yahoo.com) -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay domain -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 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [98.138.229.113 listed in list.dnswl.org] 0.2 AWL AWL: From: address is in the auto white-list X-Headers-End: 1RrVsL-00043D-MH Subject: [Bitcoin-development] Controlled block generation in fuzzer for testing blockchain X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list Reply-To: Amir Taaki List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Jan 2012 14:37:02 -0000 I added the ability to do controlled generation of blocks to gavin's fuzzer= =0A=0Ahttps://github.com/genjix/bitcoin/tree/fuzzer=0A=0A=0Abitcoind -daemo= n=0Abitcoind setfuzzpreviousblock=A0000000000019d6689c085ae165831e934ff763a= e46a2a6c172b3f1b60a8ce26f=0Abitcoind setgenerate true=0A=0AIt will start ha= shing the block with the previous hash field set to=A0000000000019d6689c085= ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f and the target as 0x1d0000ff=0A= =0AOn completion it will dump the hex value of the block to debug.log and e= xit.=0A=0AYou can then feed that block to your implementation in whatever c= ontrolled manner you wish (i.e with libbitcoin I made a simple tool in a fe= w lines to read the hex and send it via the network in localhost). If anyon= e wants the libbitcoin tool then let me know and i'll paste it over on IRC.