summaryrefslogtreecommitdiff
path: root/b3/5045641984bde78bfeee871e89d50444c2ab69
blob: bd49d35b57f66810e6102a849bea63d5d836a60f (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
	helo=mx.sourceforge.net)
	by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <envelope@gim.name>) id 1QhWrj-0007qc-Ew
	for bitcoin-development@lists.sourceforge.net;
	Fri, 15 Jul 2011 01:06:51 +0000
X-ACL-Warn: 
Received: from smtpfb1-g21.free.fr ([212.27.42.9])
	by sog-mx-2.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
	id 1QhWrh-0003CA-UO for bitcoin-development@lists.sourceforge.net;
	Fri, 15 Jul 2011 01:06:51 +0000
Received: from smtp5-g21.free.fr (smtp5-g21.free.fr [212.27.42.5])
	by smtpfb1-g21.free.fr (Postfix) with ESMTP id 2EAFC2D5C8
	for <bitcoin-development@lists.sourceforge.net>;
	Fri, 15 Jul 2011 02:48:36 +0200 (CEST)
Received: from tenebreuse.gim.name (unknown [82.229.193.250])
	by smtp5-g21.free.fr (Postfix) with ESMTP id 88CA9D4801C
	for <bitcoin-development@lists.sourceforge.net>;
	Fri, 15 Jul 2011 02:48:26 +0200 (CEST)
Received: by tenebreuse.gim.name (Postfix, from userid 1000)
	id AC2F5DFAD; Fri, 15 Jul 2011 02:48:24 +0200 (CEST)
Date: Fri, 15 Jul 2011 02:48:24 +0200
From: =?utf-8?B?U3TDqXBoYW5l?= Gimenez <dev@gim.name>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Message-ID: <20110715004824.GA697585@tenebreuse>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
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.
X-Headers-End: 1QhWrh-0003CA-UO
Subject: [Bitcoin-development] Listing of generation transactions
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Fri, 15 Jul 2011 01:06:51 -0000

Hello all,

After reading pull/417, I'm noticing that generation transactions
always appear twice in listtransaction output:

 * one item with account "" and category "generate"/"imature"/"orphan",
   plus some transaction data.

 * one with the account associated to the destination address and
   category "received", plus the same transaction data.

Both items have the same txid.

Is this the intended behavior or should the second be removed?

Also, why is account "" enforced in the first item?
(Wrong assumption that coinbase is always built from the client
itself?).

Last, it happens that {list,get}receivedby{address,account} commands
never list or take into account generation transactions. I'm not sure
how the help message associated to those commands should be
understood. As a user, I would assume that generated transaction are
included in these listings/amounts.

Is all this related with some issues encountered by E-wallet
providers?

Thanks,
St=C3=A9phane