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

Tendermint consensus does not generate blocks if the network is disabled #227

Open
majecty opened this issue Mar 3, 2020 · 0 comments
Open
Labels
bug Something isn't working consensus Consensus

Comments

@majecty
Copy link
Contributor

majecty commented Mar 3, 2020

If we use the solo consensus engine, it can generate blocks even though the network is disabled. The Tendermint consensus engine, however, does not generate blocks if the network is disabled.

Actually, since a normal network will be able to enable the network, this is not an important issue. If a user wants to run a network with only one Tendermint node to test some feature, this can matter.

What I mean by disabling/enabling the network is changing the "disable" value in the config file:

@majecty majecty added bug Something isn't working consensus Consensus labels Mar 3, 2020
@majecty majecty changed the title Tendermint consensus does not generates block if network is disabled Tendermint consensus does not generate blocks if network is disabled Mar 3, 2020
@ScarletBlue ScarletBlue changed the title Tendermint consensus does not generate blocks if network is disabled Tendermint consensus does not generate blocks if the network is disabled Mar 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working consensus Consensus
Projects
None yet
Development

No branches or pull requests

1 participant