Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[PATCH] Treat generation (mined) transactions less different from receive transactions #89

Closed
wants to merge 1 commit into from

Conversation

merlin83
Copy link

@merlin83 merlin83 commented Jan 3, 2014

  • Show address receiving the generation, and include it in the correct "account"
  • Multiple entries in listtransactions output if the coinbase has multiple outputs to us

This is from a diff of commit 0050cf2 from litecoin, updated to apply cleanly to dogecoin

This fixes the situation when mined coins are credited to the default account in the wallets and appear with the Address: (n/a) in the qt client.

…eive transactions

- Show address receiving the generation, and include it in the correct "account"
- Multiple entries in listtransactions output if the coinbase has multiple outputs to us

This is from a diff of commit 0050cf2 from litecoin, updated to apply cleanly to dogecoin
@asadhaider
Copy link
Contributor

Awesome, I hope this works. The correct litecoin commit is litecoin-project/litecoin@0050cf2.

@ummjackson
Copy link
Contributor

[Automated Message] We believe this issue has been addressed as part of the Dogecoin v1.5 update, currently in alpha. It builds on top of the latest Litecoin code base, bringing a range of improvements. Please review the active development repository at https://github.com/ummjackson/dogecoin-1_5_alpha (click "Releases" for up-to-date binaries) and if you still find issues, please report them or submit a pull request there. The 1.5 repository will overwrite the outdated 1.4.1 code base once tested and finalized. We will not be merging further pull requests on the 1.4 code base. Thanks for all your support, we really look forward to releasing 1.5 to the public!

@ummjackson ummjackson closed this Jan 26, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants