Skip to content
This repository has been archived by the owner on Aug 2, 2022. It is now read-only.

Allow p2p incomming connections when in read only mode #7956

Closed

Conversation

elmato
Copy link
Contributor

@elmato elmato commented Sep 20, 2019

Change Description

Consensus Changes

  • Consensus Changes

API Changes

  • API Changes

Documentation Additions

  • Documentation Additions

@heifner
Copy link
Contributor

heifner commented Sep 23, 2019

Can you provide your use case for enabling this behavior. The point of a read only node is so it can feed plugins not to do any validation on transactions/blocks.

@elmato
Copy link
Contributor Author

elmato commented Sep 23, 2019

The use case is to offer a read-only peering mode where clients can sync to the chain but they are not allowed to to push transactions using that channel.

This is useful for some sidechains that wants to let user get in sync with the chain, but they have to push transactions through over another channel (UI / RPC)

Copy link
Contributor

@NorseGaud NorseGaud left a comment

Choose a reason for hiding this comment

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

Misspelling: incomming should be incoming

@heifner
Copy link
Contributor

heifner commented Dec 18, 2019

The use case is to offer a read-only peering mode where clients can sync to the chain but they are not allowed to to push transactions using that channel.

This is useful for some sidechains that wants to let user get in sync with the chain, but they have to push transactions through over another channel (UI / RPC)

Can't they just not load the chain_api_plugin ?

@swatanabe-b1
Copy link
Contributor

Can we close this? It should be resolved by #8743, right?

@heifner heifner closed this Apr 7, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants