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-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1RqRJW-0006jR-Jq for bitcoin-development@lists.sourceforge.net; Thu, 26 Jan 2012 15:32:38 +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=gavinandresen@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 1RqRJR-0003eT-L9 for bitcoin-development@lists.sourceforge.net; Thu, 26 Jan 2012 15:32:38 +0000 Received: by mail-ww0-f53.google.com with SMTP id dr12so685768wgb.10 for ; Thu, 26 Jan 2012 07:32:33 -0800 (PST) MIME-Version: 1.0 Received: by 10.216.138.149 with SMTP id a21mr200371wej.0.1327591953283; Thu, 26 Jan 2012 07:32:33 -0800 (PST) Received: by 10.223.112.199 with HTTP; Thu, 26 Jan 2012 07:32:33 -0800 (PST) In-Reply-To: <1327534072.49535.YahooMailNeo@web121001.mail.ne1.yahoo.com> References: <1327534072.49535.YahooMailNeo@web121001.mail.ne1.yahoo.com> Date: Thu, 26 Jan 2012 10:32:33 -0500 Message-ID: From: Gavin Andresen To: Amir Taaki Content-Type: multipart/alternative; boundary=001636eeecadc838c504b77016d2 X-Spam-Score: -0.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 (gavinandresen[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message -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 X-Headers-End: 1RqRJR-0003eT-L9 Cc: "bitcoin-development@lists.sourceforge.net" Subject: Re: [Bitcoin-development] Fuzzer? 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: Thu, 26 Jan 2012 15:32:38 -0000 --001636eeecadc838c504b77016d2 Content-Type: text/plain; charset=ISO-8859-1 https://github.com/gavinandresen/bitcoin-git/tree/fuzzer It is a transaction fuzzer; adding block fuzzing is on the TODO. Basic usage is: 1. Use the send* RPC commands to get one or more transaction IDs 2. Run a script that repeatedly calls relayfuzzed with a nonce/txid ... and see how the connected peer(s) react to all the fuzzy 'inv/tx' protocol messages. I built it to stress-test BIP 16, there are lots of useful features that could be added. Patches welcome! -- -- Gavin Andresen --001636eeecadc838c504b77016d2 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable https:= //github.com/gavinandresen/bitcoin-git/tree/fuzzer

I= t is a transaction fuzzer; adding block fuzzing is on the TODO.

Basic usage is:
1. Use the send* RPC commands to g= et one or more transaction IDs
2. Run a script that repeatedly ca= lls relayfuzzed with a nonce/txid
... and see how the connected p= eer(s) react to all the fuzzy 'inv/tx' protocol messages.

I built it to stress-test BIP 16, there are lots of useful features tha= t could be added. =A0Patches welcome!

--
--
Gavin Andresen

--001636eeecadc838c504b77016d2--