Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1RIOMy-00051d-9X for bitcoin-development@lists.sourceforge.net; Mon, 24 Oct 2011 17:31:28 +0000 X-ACL-Warn: Received: from out5.smtp.messagingengine.com ([66.111.4.29]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1RIOMx-000542-0m for bitcoin-development@lists.sourceforge.net; Mon, 24 Oct 2011 17:31:28 +0000 Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 9430620908 for ; Mon, 24 Oct 2011 13:14:10 -0400 (EDT) Received: from frontend1.nyi.mail.srv.osa ([10.202.2.160]) by compute3.internal (MEProxy); Mon, 24 Oct 2011 13:14:10 -0400 X-Sasl-enc: 6Gbf3K/usqW2fP/Cmx9459JkEhBcU9pbYlvyUKJxwSVX 1319476450 Received: from mail-wy0-f175.google.com (mail-wy0-f175.google.com [74.125.82.175]) by mail.messagingengine.com (Postfix) with ESMTPSA id 4976740BEFA for ; Mon, 24 Oct 2011 13:14:10 -0400 (EDT) Received: by wyg19 with SMTP id 19so9411192wyg.34 for ; Mon, 24 Oct 2011 10:14:09 -0700 (PDT) MIME-Version: 1.0 Received: by 10.227.11.75 with SMTP id s11mr9837551wbs.62.1319476449586; Mon, 24 Oct 2011 10:14:09 -0700 (PDT) Received: by 10.180.96.101 with HTTP; Mon, 24 Oct 2011 10:14:09 -0700 (PDT) In-Reply-To: References: <44861.134.106.52.172.1319444997.squirrel@webmail.uni-osnabrueck.de> Date: Mon, 24 Oct 2011 11:14:09 -0600 Message-ID: From: Michael Hendricks To: Gavin Andresen Content-Type: multipart/alternative; boundary=002215974d36112e1904b00e8d5b X-Spam-Score: 1.0 (+) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. 1.0 HTML_MESSAGE BODY: HTML included in message 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: 1RIOMx-000542-0m Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Determine input addresses of a transaction 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: Mon, 24 Oct 2011 17:31:28 -0000 --002215974d36112e1904b00e8d5b Content-Type: text/plain; charset=UTF-8 On Mon, Oct 24, 2011 at 8:55 AM, Gavin Andresen wrote: > If you assume the client has all previous transactions, then you could > get the transaction input's prevout (from the memory pool or disk) and > then ExtractAddress() from it. That is probably a bad idea for > listtransactions, since fetching all the previous inputs from disk > just so you can check to see if they're 'green' violates the "a > feature shouldn't cost anything if it is not being used" design > principle. > Are there current users of gettransaction for whom the performance penalty would be problematic? If so, perhaps gettransaction could take an optional second argument includeinputaddresses which defaults to false. -- Michael --002215974d36112e1904b00e8d5b Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On Mon, Oct 24, 2011 at 8:55 AM, Gavin Andresen = <gavinandre= sen@gmail.com> wrote:
If you as= sume the client has all previous transactions, then you could
get the transaction input's prevout (from the memory pool or disk) and<= br> then ExtractAddress() from it. That is probably a bad idea for
listtransactions, since fetching all the previous inputs from disk
just so you can check to see if they're 'green' violates the &q= uot;a
feature shouldn't cost anything if it is not being used" design principle.

Are there current users of gettransaction for whom the = performance penalty would be problematic? =C2=A0If so, perhaps gettransacti= on could take an optional second argument includeinputaddresses which defau= lts to false.

--=C2=A0
Michael
--002215974d36112e1904b00e8d5b--