This repository has been archived by the owner on Aug 2, 2022. It is now read-only.
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.
Change Description
--read-mode
isread-only
andirreversible
. Incoming connections were originally intended to be prevented to avoid accidental connections from external clients who would have no indication that their transactions were not being evaluated or forwarded on the p2p network. However, this restriction was not actually enforced in v1.8.x. [Feature request]Need a new mode for private peering network - 2.0.1 release read-only node not listen on p2p port(9876) #8580 indicates there are valid use cases for allowing incoming connections. Specifically if you are wanting to setup a relay node between two block producers where transactions do not need to flow as they come in through other relay nodes that are not in read-only mode.Consensus Changes
API Changes
Documentation Additions