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-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Qi8Rw-0001BN-5A for bitcoin-development@lists.sourceforge.net; Sat, 16 Jul 2011 17:14:44 +0000 X-ACL-Warn: Received: from zinan.dashjr.org ([173.242.112.54]) by sog-mx-4.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1Qi8Rr-0002ZE-8a for bitcoin-development@lists.sourceforge.net; Sat, 16 Jul 2011 17:14:44 +0000 Received: from ishibashi.localnet (fl-67-77-87-241.dhcp.embarqhsd.net [67.77.87.241]) (Authenticated sender: luke-jr) by zinan.dashjr.org (Postfix) with ESMTPSA id 487A8D90048 for ; Sat, 16 Jul 2011 17:14:29 +0000 (UTC) From: "Luke-Jr" To: Bitcoin Dev Date: Sat, 16 Jul 2011 13:14:11 -0400 User-Agent: KMail/1.13.7 (Linux/2.6.39-gentoo; KDE/4.6.4; x86_64; ; ) X-PGP-Key-Fingerprint: CE5A D56A 36CC 69FA E7D2 3558 665F C11D D53E 9583 X-PGP-Key-ID: 665FC11DD53E9583 X-PGP-Keyserver: x-hkp://subkeys.pgp.net MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Message-Id: <201107161314.13267.luke@dashjr.org> 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 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain 0.0 AWL AWL: From: address is in the auto white-list X-Headers-End: 1Qi8Rr-0002ZE-8a Subject: [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 17:14:44 -0000 Example patch: http://tinyurl.com/6679go5 Changes: * Additions to your wallet always are category:"receive", no matter what kind of transaction * Generated coins have an extra key, from:"generation" * All transactions have a new key, status: * "orphan" -- Another block chain invalidated this transaction (only for generation?) * "validating" -- Default stage for transactions; 0-2 confirmations for ordinary sends, and 0-100 for generated coins * "processing" -- 3-6 confirms for ordinary sends; 101-120 for generated * "confirmed" -- over 6/120 confirmations * "expired" -- for ordinary sends that have timed out without getting into a block, or had its inputs otherwise respent This change is proposed to fix webservices being ignorant of generated transactions by keeping a standard category/format for all similar types of entries. Thoughts?