Skip to content
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

Merged
merged 1 commit into from Apr 2, 2020

Conversation

maflcko
Copy link
Member

@maflcko maflcko commented Mar 29, 2020

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.

Copy link
Contributor

@jonatack jonatack left a 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

doc/reduce-traffic.md Outdated Show resolved Hide resolved
doc/reduce-memory.md Outdated Show resolved Hide resolved
doc/reduce-memory.md Outdated Show resolved Hide resolved
@maflcko
Copy link
Member Author

maflcko commented Mar 29, 2020

Addressed feedback by @jonatack

@jonatack
Copy link
Contributor

ACK fae5d88

Copy link
Member

@hebasto hebasto left a 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".

doc/reduce-memory.md Outdated Show resolved Hide resolved
doc/reduce-traffic.md Outdated Show resolved Hide resolved
Co-Authored-By: Hennadii Stepanov <32963518+hebasto@users.noreply.github.com>
Copy link
Member

@hebasto hebasto left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ACK fa6e01f

@jonatack
Copy link
Contributor

jonatack commented Mar 30, 2020

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.

@maflcko maflcko merged commit 0d71395 into bitcoin:master Apr 2, 2020
@maflcko maflcko deleted the 2003-docBlockRelayOnly branch April 2, 2020 21:31
sidhujag pushed a commit to syscoin/syscoin that referenced this pull request Apr 3, 2020
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
deadalnix pushed a commit to Bitcoin-ABC/bitcoin-abc that referenced this pull request Jan 14, 2021
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
@bitcoin bitcoin locked as resolved and limited conversation to collaborators Feb 15, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants