Fix longpoll getblocktemplate not getting notified if a block is pushed via submitblock #488
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
btcd currently does not notify miners waiting for new block templates via longpolling when a block is pushed via submitblock RPC. It does when a block is received via the P2P protocol.
This is due to the code paths for connecting the block being different. The fix adds a call to NotifyBlockConnected in the submitblock code path, as in handleBlockMsg.
This bug is hard to see in regular conditions: mainnet difficulty is too high, and regtest/simnet is way too low. Maybe it'd be possible to reproduce it in testnet. In the logs below I'm solo mining on a test blockchain with a target of 0000000ffff000.., 16x easier than the Bitcoin difficulty.
Logs before the fix:
btcd:
minerd:
Logs after the fix
btcd:
minerd: