Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1SwDP5-0006MB-24 for bitcoin-development@lists.sourceforge.net; Tue, 31 Jul 2012 14:26:31 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.214.175 as permitted sender) client-ip=209.85.214.175; envelope-from=pieter.wuille@gmail.com; helo=mail-ob0-f175.google.com; Received: from mail-ob0-f175.google.com ([209.85.214.175]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1SwDP1-0004gE-Dy for bitcoin-development@lists.sourceforge.net; Tue, 31 Jul 2012 14:26:31 +0000 Received: by obcva7 with SMTP id va7so11105103obc.34 for ; Tue, 31 Jul 2012 07:26:21 -0700 (PDT) MIME-Version: 1.0 Received: by 10.182.192.41 with SMTP id hd9mr23767700obc.17.1343744781870; Tue, 31 Jul 2012 07:26:21 -0700 (PDT) Received: by 10.76.9.129 with HTTP; Tue, 31 Jul 2012 07:26:21 -0700 (PDT) In-Reply-To: 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: Tue, 31 Jul 2012 16:26:21 +0200 Message-ID: From: Pieter Wuille To: Gavin Andresen Content-Type: text/plain; charset=ISO-8859-1 X-Spam-Score: -1.1 (-) 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 (pieter.wuille[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 0.5 AWL AWL: From: address is in the auto white-list X-Headers-End: 1SwDP1-0004gE-Dy 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Jul 2012 14:26:31 -0000 On Mon, Jul 30, 2012 at 2:52 AM, Gavin Andresen wrote: > 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. Ultraprune changes the block validation mechanism to only use a set of coins and the latest block pointer as state. This state is represented by an abstract class with several implementations. It would be easy to have a testset run with a memory-backed coin set as state, with the list of coins and blocks loaded from a file. -- Pieter