Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 8264E129D for ; Tue, 1 Sep 2015 16:59:21 +0000 (UTC) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from cock.li (cock.li [176.9.0.140]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 064EB274 for ; Tue, 1 Sep 2015 16:59:20 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Date: Tue, 01 Sep 2015 16:59:15 +0000 From: Monarch To: bitcoin-dev@lists.linuxfoundation.org In-Reply-To: References: Message-ID: X-Sender: monarch@cock.li User-Agent: Roundcube Webmail/0.9.5 X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,T_RP_MATCHES_RCVD autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org Subject: Re: [bitcoin-dev] push tx fuzzing X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Development Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Sep 2015 16:59:21 -0000 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.