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

Use blockHash for AcceptedWorkID, not powHash. #416

Merged
merged 2 commits into from
Oct 18, 2023

Conversation

jholdstock
Copy link
Member

blockHash is used to construct the AcceptedWorkID when retrieving AcceptedWork from the database, not the powHash.

Because of this bug, dcrpool was failing to register when a block mined by the pool had been confirmed, thus it was never sending the coinbase from that block to the mining participants.

pool/client.go Outdated Show resolved Hide resolved
As of DCP-0011, dcrpool now has to deal with two types of hash - block
hash and pow hash. To reduce the chance of confusion, this renames
"hash" to "powHash" where appropriate.
blockHash is used to construct the AcceptedWorkID when retrieving
AcceptedWork from the database, not the powHash.

Because of this bug, dcrpool was failing to register when a block mined
by the pool had been confirmed, thus it was never sending the coinbase
from that block to the mining participants.
@davecgh
Copy link
Member

davecgh commented Oct 18, 2023

Good update with the rename to powHash. I was actually thinking the same thing!

@jholdstock jholdstock merged commit 7b3cdc6 into decred:master Oct 18, 2023
2 checks passed
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.

2 participants