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
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <gavinandresen@gmail.com>) id 1SveDs-0004vY-8G
for bitcoin-development@lists.sourceforge.net;
Mon, 30 Jul 2012 00:52:36 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.215.47 as permitted sender)
client-ip=209.85.215.47; envelope-from=gavinandresen@gmail.com;
helo=mail-lpp01m010-f47.google.com;
Received: from mail-lpp01m010-f47.google.com ([209.85.215.47])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1SveDr-00023l-GG
for bitcoin-development@lists.sourceforge.net;
Mon, 30 Jul 2012 00:52:36 +0000
Received: by lags15 with SMTP id s15so3095213lag.34
for <bitcoin-development@lists.sourceforge.net>;
Sun, 29 Jul 2012 17:52:29 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.152.109.198 with SMTP id hu6mr9697192lab.21.1343609548865;
Sun, 29 Jul 2012 17:52:28 -0700 (PDT)
Received: by 10.112.17.163 with HTTP; Sun, 29 Jul 2012 17:52:28 -0700 (PDT)
In-Reply-To: <50157450.8070806@justmoon.de>
References: <1343579466.30862.YahooMailNeo@web121004.mail.ne1.yahoo.com>
<501565D5.4060608@justmoon.de>
<1343580154.34128.YahooMailNeo@web121004.mail.ne1.yahoo.com>
<50157450.8070806@justmoon.de>
Date: Sun, 29 Jul 2012 20:52:28 -0400
Message-ID: <CABsx9T016OmU2qU1a67=YmpA4VDbzrddOamc8=Mt6x7BhVO1Uw@mail.gmail.com>
From: Gavin Andresen <gavinandresen@gmail.com>
To: Stefan Thomas <moon@justmoon.de>
Content-Type: text/plain; charset=ISO-8859-1
X-Spam-Score: -1.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
-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: 1SveDr-00023l-GG
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] script tests - invalid script in
script_valid.json?
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Mon, 30 Jul 2012 00:52:36 -0000
> Is there interest to port more tests (P2SH, checksig, checkmultisig,
> block verification, maybe even DoS rules) into data-driven format? It
> might be something that I'd like to help with if pull requests in that
> direction are welcome.
Yes, more tests are definitely welcome.
check*sig tests are tricky, because they have to refer to previous
unspent transactions and private keys (so require a particular block
chain to test against). Brilliant ideas on a simple data-driven format
welcome.
block verification tests would be great; a collection of good/bad
block chains, starting from a common chain (maybe the testnet3
tesnet-in-a-box chain) would be very useful for regression testing.
--
--
Gavin Andresen
|
