From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1QiB1H-0008Qy-3k for bitcoin-development@lists.sourceforge.net; Sat, 16 Jul 2011 19:59:23 +0000 X-ACL-Warn: Received: from smtp5-g21.free.fr ([212.27.42.5]) by sog-mx-3.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1QiB1D-0007XV-Ex for bitcoin-development@lists.sourceforge.net; Sat, 16 Jul 2011 19:59:23 +0000 Received: from tenebreuse.gim.name (unknown [82.229.193.250]) by smtp5-g21.free.fr (Postfix) with ESMTP id 11F16D4806C for ; Sat, 16 Jul 2011 21:59:08 +0200 (CEST) Received: by tenebreuse.gim.name (Postfix, from userid 1000) id 909B2FDEC; Sat, 16 Jul 2011 21:59:07 +0200 (CEST) Date: Sat, 16 Jul 2011 21:59:07 +0200 From: =?utf-8?B?U3TDqXBoYW5l?= Gimenez To: Bitcoin Dev Message-ID: <20110716195907.GA311029@tenebreuse> References: <201107161314.13267.luke@dashjr.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <201107161314.13267.luke@dashjr.org> User-Agent: Mutt/1.5.21 (2010-09-15) Content-Transfer-Encoding: quoted-printable X-Spam-Score: 0.0 (/) 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 [212.27.42.5 listed in list.dnswl.org] X-Headers-End: 1QiB1D-0007XV-Ex Subject: Re: [Bitcoin-development] [RFC] listtransactions reformatting 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: Sat, 16 Jul 2011 19:59:23 -0000 Hi, You may have a look at the following proposal. It associates generations txouts with the appropriate addresses and accounts. (See my previous mail) https://github.com/sgimenez/bitcoin/commit/a8e6510042f2f7f951414c7da12466= 8b30da4acd > * Additions to your wallet always are category:"receive", no matter > what kind of transaction Either this, or maybe webservices should be told to forget about categories and to rely only on the sign of the amounts. Maybe a "type" field with values "credit"/"debit" could help them? This way, more categories could be added later (escrow transactions, or other scripts that might be standardized). An official API guide (not just a technical reference) would be very valuable here. Last, I agree that {list,get}receivedby* should include generated amounts, because there is currently no way to do this for generations. (This issue is not addressed by my patch yet) Best, St=C3=A9phane