From: Monarch <monarch@cock•li>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] push tx fuzzing
Date: Tue, 01 Sep 2015 16:59:15 +0000 [thread overview]
Message-ID: <e5c1d53a1387dce141d30c9eee6ee2ce@cock.li> (raw)
In-Reply-To: <CAGH37S+daPddzwo1bJ0sPs3RfLOE63TPkCrc-X6qhNw7nu6=Xg@mail.gmail.com>
On 2015-09-01 15:50, Kristov Atlas via bitcoin-dev wrote:
> I am interested in finding or writing a fuzzer for push tx APIs. I did
> not find one after a brief search. Has anyone found otherwise, or is
> she in the process of writing one?
>
https://github.com/jonasnick/bitcoinconsensus_testcases
https://jonasnick.github.io/blog/2015/05/09/fuzzing-bitcoin-consensus/
The only implementations with any significant network presence are
btcd and Bitcoin Core, fuzzing them should be sufficient if these
services are doing validation of transactions using one of the two.
For example two of the ones you have linked are based in Insight,
which uses Bitcoin Core for validation. If they aren't validating
transactions before broadcast they won't make it more than a single
hop through the P2P the network so they are of minimum concern.
next prev parent reply other threads:[~2015-09-01 16:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-01 15:50 Kristov Atlas
2015-09-01 16:59 ` Monarch [this message]
2015-09-01 18:03 ` Wladimir J. van der Laan
2015-09-01 18:22 ` Manuel Aráoz
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=e5c1d53a1387dce141d30c9eee6ee2ce@cock.li \
--to=monarch@cock$(echo .)li \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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