summaryrefslogtreecommitdiff
path: root/de/4f3a741e684f4f65dc6623bb830c00a490ee1b
blob: 9762c84f6364654d3e02d87f1b1b3ded928fd241 (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
81
Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192]
	helo=mx.sourceforge.net)
	by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <envelope@gim.name>) id 1Qhkwa-0007E9-Pm
	for bitcoin-development@lists.sourceforge.net;
	Fri, 15 Jul 2011 16:08:48 +0000
X-ACL-Warn: 
Received: from smtp5-g21.free.fr ([212.27.42.5])
	by sog-mx-2.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
	id 1QhkwY-00084O-14 for bitcoin-development@lists.sourceforge.net;
	Fri, 15 Jul 2011 16:08:48 +0000
Received: from tenebreuse.gim.name (unknown [82.229.193.250])
	by smtp5-g21.free.fr (Postfix) with ESMTP id 1D870D48111
	for <bitcoin-development@lists.sourceforge.net>;
	Fri, 15 Jul 2011 18:08:35 +0200 (CEST)
Received: by tenebreuse.gim.name (Postfix, from userid 1000)
	id A72DCF241; Fri, 15 Jul 2011 18:08:34 +0200 (CEST)
Date: Fri, 15 Jul 2011 18:08:34 +0200
From: =?utf-8?B?U3TDqXBoYW5l?= Gimenez <dev@gim.name>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Message-ID: <20110715160834.GA5822@tenebreuse>
References: <20110715004824.GA697585@tenebreuse>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20110715004824.GA697585@tenebreuse>
User-Agent: Mutt/1.5.21 (2010-09-15)
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: 1QhkwY-00084O-14
Subject: Re: [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 16:08:48 -0000

> 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.

Sorry! the item duplication was due to the pull. (very stupid me)

The issue with account "" remains.

For coinbase transactions, we may list one "generated" item per txout
that corresponds to an owned address. Accounts would be associated
accordingly, in the same way as for usual "received" amounts. Account
balances would also take into account these generated amounts in the
obvious way.

Would that be ok? I think few people rely on these specific details,
and they would be happy with such a change. Moreover, this would
actually simplify the code a little bit.


> 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?