Use interruptWait() to speed up ctrl + c #57
Merged
+35
−6
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Co-authored-by: ismaelsadeeq <abubakarsadiqismail@proton.me>
bitcoin/bitcoin#33676 adds interruptWait() to the Mining interface. Call this method for quicker shutdown. This change is backward compatible with the currently released version Bitcoin Core v30. If the new IPC method doesn't exist, it falls back to the previous behavior of just waiting for waitNext() to return after -sv2interval.
Sjors
force-pushed
the
2025/10/interrupt-wait
branch
from
b4c7d97 to
8c2c9f6
Compare
Collaborator
Author
|
Waiting for the upstream PR to be merged before merging this. |
Collaborator
Author
|
bitcoin/bitcoin#33676 was just merged |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
bitcoin/bitcoin#33676 adds
interruptWait()to the Mining interface. Call this method for quicker shutdown.This change is backward compatible with the currently released version Bitcoin Core v30. If the new IPC method doesn't exist, it falls back to the previous behavior of just waiting for
waitNext()to return after-sv2interval.To reproduce you need to connect to a Bitcoin Core node and also have the SRI pool (or JDC) role connect to you. See e.g. the first couple of steps in this tutorial: https://github.com/Sjors/sv2-workshop