-
Notifications
You must be signed in to change notification settings - Fork 35.6k
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
ZMQ rawblock doesn't publish new block in case of chainsplit. #20376
Comments
If I understand you correctly, the block at height 656477 with the hash The ZMQ documentation lists a few remarks about the ZMQ interface. One of them is:
Based on the documentation I'd say that |
@0xB10C Well spotted, thanks! If this behavior is intended to continue, feel free to close this issue. |
0xB10C pointed out above this is intended behavior and also related PR #19572 has been merged. It looks like this issue can be closed. |
Expected behavior
I expect ZMQ raw block subscription to publish every raw block even in the case of a chainplit. Today two blocks (656477-8, with tip hash
00000000000000000005f8f74e57aa4584aacfed509b8a6feb20bc22e7d60a34
) were orphaned and I decided to check my bitcoin node logs to see how it behaved during this event.Actual behavior
The node published a ZMQ notification for block 656476 and the first 656477 block it received at 18:47:39Z. Around 9 minutes later, the node receives blocks 656477 and 656478 that orphan the previous 656477 block. From the log, we see that the zmq notification for the second 656477 block was not published:
To reproduce
Check your own logs if you had block zmq and
debug=zmq
enabled or reproduce a chainsplit on regtest.System information
Bitcoin core v0.20.1 running on Ubuntu 18.04
The text was updated successfully, but these errors were encountered: