From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1QiHdC-0007gu-3r for bitcoin-development@lists.sourceforge.net; Sun, 17 Jul 2011 03:02:58 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.210.46 as permitted sender) client-ip=209.85.210.46; envelope-from=gavinandresen@gmail.com; helo=mail-pz0-f46.google.com; Received: from mail-pz0-f46.google.com ([209.85.210.46]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1QiHdB-0007sV-Dz for bitcoin-development@lists.sourceforge.net; Sun, 17 Jul 2011 03:02:58 +0000 Received: by pzk3 with SMTP id 3so2934657pzk.5 for ; Sat, 16 Jul 2011 20:02:51 -0700 (PDT) MIME-Version: 1.0 Received: by 10.142.79.12 with SMTP id c12mr2446904wfb.443.1310871771340; Sat, 16 Jul 2011 20:02:51 -0700 (PDT) Received: by 10.142.163.9 with HTTP; Sat, 16 Jul 2011 20:02:51 -0700 (PDT) In-Reply-To: <201107161603.08960.luke@dashjr.org> References: <201107161314.13267.luke@dashjr.org> <20110716195907.GA311029@tenebreuse> <201107161603.08960.luke@dashjr.org> Date: Sun, 17 Jul 2011 13:02:51 +1000 Message-ID: From: Gavin Andresen To: bitcoin-development@lists.sourceforge.net Content-Type: text/plain; charset=ISO-8859-1 X-Spam-Score: -0.8 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. 1.5 TVD_PH_BODY_ACCOUNTS_PRE BODY: TVD_PH_BODY_ACCOUNTS_PRE -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.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 T_TO_NO_BRKTS_FREEMAIL To: misformatted and free email service -0.8 AWL AWL: From: address is in the auto white-list X-Headers-End: 1QiHdB-0007sV-Dz 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: Sun, 17 Jul 2011 03:02:58 -0000 Fixing listtransactions (and listreceivedby/etc) so coin generation transactions to particular addresses/accounts are credited to that address/account is a good idea. I don't think changing listtransactions output would be on the priority list for any web services operators (in fact, I think most would scream bloody murder if the output changed in a way that forced them to change their code). The accounts-related things that I think ARE on their high-priority list are: 1) Fixing getbalance and listtransactions performance problems when you have hundreds of thousands of transactions and thousands of accounts. 2) push-notification of coins received to accounts, so they don't have to poll for changes. -- -- Gavin Andresen