doc: clarify ZMQ data scope statement for accuracy#248
Open
8144225309 wants to merge 1 commit intobitcoinknots:29.x-knotsfrom
Open
doc: clarify ZMQ data scope statement for accuracy#2488144225309 wants to merge 1 commit intobitcoinknots:29.x-knotsfrom
8144225309 wants to merge 1 commit intobitcoinknots:29.x-knotsfrom
Conversation
The existing statement about ZMQ data scope predates the wallet publisher additions. This adjusts the wording to accurately reflect which notifications contain P2P-sourced data vs wallet-sourced data.
Ari4ka
approved these changes
Feb 15, 2026
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
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.
The existing statement about ZMQ data scope predates the wallet publisher additions. This adjusts the wording to accurately reflect which notifications contain P2P-sourced data vs wallet-sourced data.
No functionality change - documentation only.