From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Svr9j-0006ku-Q2 for bitcoin-development@lists.sourceforge.net; Mon, 30 Jul 2012 14:41:11 +0000 X-ACL-Warn: Received: from nm29.bullet.mail.ne1.yahoo.com ([98.138.90.92]) by sog-mx-2.v43.ch3.sourceforge.com with smtp (Exim 4.76) id 1Svr9i-0006LG-QK for bitcoin-development@lists.sourceforge.net; Mon, 30 Jul 2012 14:41:11 +0000 Received: from [98.138.90.56] by nm29.bullet.mail.ne1.yahoo.com with NNFMP; 30 Jul 2012 14:41:05 -0000 Received: from [98.138.87.9] by tm9.bullet.mail.ne1.yahoo.com with NNFMP; 30 Jul 2012 14:41:05 -0000 Received: from [127.0.0.1] by omp1009.mail.ne1.yahoo.com with NNFMP; 30 Jul 2012 14:41:05 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 127526.14897.bm@omp1009.mail.ne1.yahoo.com Received: (qmail 13698 invoked by uid 60001); 30 Jul 2012 14:41:04 -0000 X-YMail-OSG: Wql25JcVM1kENE4YaG1SuUJ6iREz8jZCp1B_bWZ6TCH0dtL 8dCg_WdXQBJ8CpP5uRu8RK4C9GG9lmwaUSCrW0KmshT.VhYhWAN8DGXIfBdP IwY8XwRRg3m1.JAMEhjQSwh216byPOnZCZJ5sLwOTtQWMJPDKjt479EwsIR2 gwbmrVzVIONMLIY0mnR4.OIVSGREkgQBjwQ0pMCorvx6p6xXjMMpWsHyIOVE OKsrFibE.WW53Dtwtw_H4Cvim0N.NtXfVreC1Gu.kTSx7gCK6.PIPJ8MKZWr jZEIZXP._p0D7FODB20__4nRimvL2Qd.bab9OVez63xIXmRmSt0A2icEHjyH 2oHLoq_i4IGkk4swQ8b0UVrJwRF9kduGGaBlorXc3CBX9RQIWCrO7nKM0yLz BBikeRCcXOrsxnwqZqOt0ZsUXJb2nzuxTNJ5Va6PS1w8p0jUV1FVMPzTYuL. GG9w4d_e6_J468z7ZoqNraa7YQ42o5raUYtoil2RRPBzQIrkT4W7LQCe2cox 5y79zzMIK0J_UWFp5CbQGk3IYTYlERZ0eOVnPswAeyzQ_4WfneA-- Received: from [201.26.113.195] by web121005.mail.ne1.yahoo.com via HTTP; Mon, 30 Jul 2012 07:41:04 PDT X-Mailer: YahooMailWebService/0.8.120.356233 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> Message-ID: <1343659264.6245.YahooMailNeo@web121005.mail.ne1.yahoo.com> Date: Mon, 30 Jul 2012 07:41:04 -0700 (PDT) From: Amir Taaki To: "bitcoin-development@lists.sourceforge.net" In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Spam-Score: 0.1 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [98.138.90.92 listed in list.dnswl.org] 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (zgenjix[at]yahoo.com) 0.2 RCVD_IN_NJABL_PROXY RBL: NJABL: sender is an open proxy [201.26.113.195 listed in combined.njabl.org] -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay domain -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 0.0 FSL_FREEMAIL_2 FSL_FREEMAIL_2 0.0 FSL_FREEMAIL_1 FSL_FREEMAIL_1 X-Headers-End: 1Svr9i-0006LG-QK 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 Reply-To: Amir Taaki List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 30 Jul 2012 14:41:11 -0000 Yep, I want to chip in and also express my gratitude for these useful tests. I sent a personal email to Gavin before. I plan to make some more complex tests by combining several of the simpler ones. ----- Original Message ----- From: Gavin Andresen To: Stefan Thomas Cc: bitcoin-development@lists.sourceforge.net Sent: Sunday, July 29, 2012 9:52 PM Subject: Re: [Bitcoin-development] script tests - invalid script in script_valid.json? > 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 ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development