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
doc: block-relay-only vs blocksonly #18464
Conversation
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.
ACK with a few additional suggestions
fa75475
to
fae5d88
Compare
Addressed feedback by @jonatack |
ACK fae5d88 |
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.
I assume that "block-relay-only" should be applied to the "connection", but not to the "peer".
Co-Authored-By: Hennadii Stepanov <32963518+hebasto@users.noreply.github.com>
080eff6
to
fa6e01f
Compare
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.
ACK fa6e01f
ACK fa6e01f pico-nit: as the outbound peer connections are called "full-relay" and "block-relay" in the debug log, perhaps use "block-relay" rather than "block-relay-only". Though the code comments use block-relay-only, the -only seems redundant, though I may be saying that out of habit of seeing "block-relay" in the log. |
fa6e01f doc: block-relay-only is not blocksonly (MarcoFalke) Pull request description: Those are different concepts, see https://github.com/bitcoin/bitcoin/blob/master/doc/release-notes/release-notes-0.19.0.1.md#p2p-changes for the block-relay-only nodes. ACKs for top commit: jonatack: ACK fa6e01f hebasto: ACK fa6e01f Tree-SHA512: 6de2c81201b62ed59e504a3a6f164068600182e1bbf63eda7f9db3160507bdba091c13882ee0e75e713f0832bfaf5973a86eba3b94588d5b72196f05ae0a9c9a
Summary: > When -blocksonly is set to 1, it interacts with the -walletbroadcast > parameter and sets it to 0 if it has not been set already.This behavior > is not captured by the current documentation, which claims that -blocksonly > does not impact any wallet transactions. > > Update the max number of outgoing peers from 8 to 10, due to the > addition of two -blocksonly peers. This is a backport of Core [[bitcoin/bitcoin#18391 | PR18391]] and [[bitcoin/bitcoin#18464 | PR18464]] Test Plan: `ninja && src/bitcoind -help` Reviewers: #bitcoin_abc, Fabien Reviewed By: #bitcoin_abc, Fabien Subscribers: Fabien Differential Revision: https://reviews.bitcoinabc.org/D8894
Those are different concepts, see https://github.com/bitcoin/bitcoin/blob/master/doc/release-notes/release-notes-0.19.0.1.md#p2p-changes for the block-relay-only nodes.