-
Notifications
You must be signed in to change notification settings - Fork 38.7k
rpc, net: Expose connections_onion_only in getnetworkinfo RPC output #20172
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
Conversation
|
The commits moved from bitcoin-core/gui#86 already have two ACKs:
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approach ACK, only skimmed the code so far but the changes look good. Needs test coverage for the new getnetworkinfo "connections_onion_only" field. Debug build is clean and I did some quick manual testing. The counts fields contain the correct values. With mixed peers:
"connections_onion_only": false,
With only onion peers:
"connections_onion_only": true,
RPC help:
"connections_onion_only" : true|false, (boolean) whether all connection are through the onion network
|
The following sections might be updated with supplementary metadata relevant to reviewers and maintainers. ConflictsReviewers, this pull request conflicts with the following ones:
If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first. |
|
Concept ACK. Agree that a functional test for |
|
Updated 174848f -> 9371757 (pr20172.01 -> pr20172.02, diff): |
3dc8e15 to
b9fc611
Compare
|
UPDATE: it was such a silly error, and I've caught it after sleep 😃 |
8d66f6c to
d301cc5
Compare
|
Updated 9371757 -> d301cc5 (pr20172.02 -> pr20172.06, diff):
Travis is green now! |
jnewbery
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One question and one small naming suggestion.
This PR contains qt-only changes. It shouldn't be too difficult to separate the changes so that PRs to the main repo only contain changes to the node code, and PRs to the GUI repo only contain changes to qt code.
Clear qt-only changes are already leaved in the GUI repo. This pull contains two commits that modify signal signatures. As these signals propagate through the qt code, I do not want to break those commits in "non-qt" and "qt" parts. |
This change prevents repetitive traversing vNodes.
ddced9f to
caebabf
Compare
|
Updated d301cc5 -> caebabf (pr20172.06 -> pr20172.09, diff):
|
|
Updated 85ff09e -> da8b109 (pr20172.10 -> pr20172.11, diff):
|
|
tACK da8b109 |
luke-jr
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Concept NACK per bitcoin-core/gui#86 (review)
|
I'm thinking about this in a context of if / when other privacy network support is added to Bitcoin Core (like I2P, #20254). What people might want then is not "are all of my connections Tor only?", but "are all of my connections using privacy networks?" and "which privacy networks are they using?". |
|
🐙 This pull request conflicts with the target branch and needs rebase. Want to unsubscribe from rebase notifications on this pull request? Just convert this pull request to a "draft". |
|
Closing. Leaving it up for grabs. |
This is a non-gui part of adding Tor icon to the GUI.
Split from bitcoin-core/gui#86 as requested:
The first approach was in #19926.