From: Gavin Andresen <gavinandresen@gmail•com>
To: Amir Taaki <zgenjix@yahoo•com>
Cc: "bitcoin-development@lists•sourceforge.net"
<bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Fuzzer?
Date: Thu, 26 Jan 2012 10:32:33 -0500 [thread overview]
Message-ID: <CABsx9T2Faoo2S8rCtqHBiM+q9nOpOxSF0zaP9yFDW6JmDwDLOw@mail.gmail.com> (raw)
In-Reply-To: <1327534072.49535.YahooMailNeo@web121001.mail.ne1.yahoo.com>
[-- Attachment #1: Type: text/plain, Size: 493 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 714 bytes --]
prev parent reply other threads:[~2012-01-26 15:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-25 23:27 Amir Taaki
2012-01-26 15:32 ` Gavin Andresen [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CABsx9T2Faoo2S8rCtqHBiM+q9nOpOxSF0zaP9yFDW6JmDwDLOw@mail.gmail.com \
--to=gavinandresen@gmail$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=zgenjix@yahoo$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox