From: "Stéphane Gimenez" <dev@gim.name>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Listing of generation transactions
Date: Fri, 15 Jul 2011 18:08:34 +0200 [thread overview]
Message-ID: <20110715160834.GA5822@tenebreuse> (raw)
In-Reply-To: <20110715004824.GA697585@tenebreuse>
> 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?
prev parent reply other threads:[~2011-07-15 16:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-15 0:48 [Bitcoin-development] Listing of generation transactions Stéphane Gimenez
2011-07-15 16:08 ` Stéphane Gimenez [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110715160834.GA5822@tenebreuse \
--to=dev@gim.name \
--cc=bitcoin-development@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox