Published on: 2011-07-15T16:08:34+00:00
The author of pull/417 has identified a recurring issue with generation transactions appearing twice in the listtransaction output. The first appearance includes transaction data, but has an account value of "" and a category of "generate"/"immature"/"orphan". The second appearance includes the same transaction data, but has the account associated with the destination address and a category of "received". Both appearances have the same txid. The author questions whether this is intentional or if the second appearance should be removed. Additionally, the author raises concerns about the enforced account value of "" in the first appearance.Furthermore, the author points out that the {list,get}receivedby{address,account} commands do not include or consider generation transactions, despite the help message suggesting otherwise. The author suggests that as a user, they would expect generated transactions to be included in these listings and amounts. The author also wonders if these issues are connected to the challenges faced by E-wallet providers.Overall, the author's observations highlight the need for clarification and potential improvements in handling generation transactions within the listtransaction output and related commands.
Updated on: 2023-08-01T02:07:30.134658+00:00