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

Coinbase transactions paid to default account. #80

Closed
minerodepicoypala opened this issue Dec 30, 2013 · 4 comments
Closed

Coinbase transactions paid to default account. #80

minerodepicoypala opened this issue Dec 30, 2013 · 4 comments

Comments

@minerodepicoypala
Copy link

This is not a bug but a feature that others coins have.

As specified in the original bitcoin protocol, generated coins are always credited to the default account. However is convenient that if the payment address belongs to an account, this generated coins should be assigned to that account, as litecoin does nowadays.

It's convenient because otherwise if the user wants to assign an account to it's mined coins it has to be done manually.

By the way, it would be useful to include in the listtransactions rpc method the address involved in each transaction (as newer clients do).

Best regards, minerodepicoypala.

@asadhaider
Copy link
Contributor

This also happens when mining using a P2P pool, coins are sent to you as generated and put in the "" (default/empty) account.

@minerodepicoypala
Copy link
Author

No in all the coins, at least in litecoin is not happening any more. This afternoon I've mined in a litecoin P2P pool and the coins appears associated to the account of the payment address, while using a dogecoin P2P pool it's assigned to the default account (paid to the payment address but not assigned to any account). I think that is not a problem of the pool is how the coin client interprets the coinbase transactions.

Please mine some litecoins with a payment address associated to an account and do the same with dogecoin.

Regards.

@asadhaider
Copy link
Contributor

Just to update this issue, a user did add a push request fixing this in #89

@minerodepicoypala
Copy link
Author

Thanks for your support.

All the best, minerodepicoypala.

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

No branches or pull requests

2 participants