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-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1RIgwo-00025v-1p for bitcoin-development@lists.sourceforge.net; Tue, 25 Oct 2011 13:21:42 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.161.47 as permitted sender) client-ip=209.85.161.47; envelope-from=gavinandresen@gmail.com; helo=mail-fx0-f47.google.com; Received: from mail-fx0-f47.google.com ([209.85.161.47]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1RIgwi-0003dW-Ji for bitcoin-development@lists.sourceforge.net; Tue, 25 Oct 2011 13:21:41 +0000 Received: by faas16 with SMTP id s16so669424faa.34 for ; Tue, 25 Oct 2011 06:21:30 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.1.137 with SMTP id 9mr1943171faf.19.1319548890339; Tue, 25 Oct 2011 06:21:30 -0700 (PDT) Received: by 10.152.24.229 with HTTP; Tue, 25 Oct 2011 06:21:30 -0700 (PDT) In-Reply-To: References: Date: Tue, 25 Oct 2011 09:21:30 -0400 Message-ID: From: Gavin Andresen To: Bitcoin Dev 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.0 T_FRT_ADULT2 BODY: ReplaceTags: Adult -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 AWL AWL: From: address is in the auto white-list X-Headers-End: 1RIgwi-0003dW-Ji Subject: Re: [Bitcoin-development] Detecting OP_EVAL scriptPubKeys that are to you 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, 25 Oct 2011 13:21:42 -0000 On Tue, Oct 25, 2011 at 6:49 AM, Mike Hearn wrote: > scriptPubKeys that use OP_EVAL contain a hash of a script. If I > understand correctly, that means to detect a transaction in a block > that is relevant to your wallet, that means you need to pre-calculate > every possible hash that might appear. You could do it that way... but that would be inefficient. You give the hash to whoever is paying you, and store the hash --> script mapping when you do that (assuming you're not using a deterministic wallet; if you are, you probably just increment a counter in the wallet). The only use case I can think of where you'd want to check for every possible hash is if you lose your wallet, you have a wallet backup that has your private keys in it, but DOES NOT have the hash --> script mapping(s). For use cases involving other people, that's probably not a problem-- you could ask them to tell you what public keys are involved, and then add them back in to the wallet (the RPC interface I settled on for m-of-n txns is an "addmultisigaddress" that takes the "m" and an array of "n" public keys, creates the script, adds the hash-->script mapping to the wallet, and returns the hash). For use cases where all the keys belong to you... either a good, automatic, in-the-cloud-backup or the equivalent of "-rescan" is needed to recover in case the mappings are lost. -- -- Gavin Andresen