blob: aa1547556faaea1bbacd5ebf740170b5386fbd32 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
|
Return-Path: <monarch@cock.li>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 8264E129D
for <bitcoin-dev@lists.linuxfoundation.org>;
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 <bitcoin-dev@lists.linuxfoundation.org>;
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 <monarch@cock.li>
To: bitcoin-dev@lists.linuxfoundation.org
In-Reply-To: <CAGH37S+daPddzwo1bJ0sPs3RfLOE63TPkCrc-X6qhNw7nu6=Xg@mail.gmail.com>
References: <CAGH37S+daPddzwo1bJ0sPs3RfLOE63TPkCrc-X6qhNw7nu6=Xg@mail.gmail.com>
Message-ID: <e5c1d53a1387dce141d30c9eee6ee2ce@cock.li>
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 <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=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.
|
