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.

Sign up for GitHub

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

Jump to bottom

Introduce the notion of consensus backend mode #3116

Closed
Tracked by #2440
kostko opened this issue Jul 19, 2020 · 0 comments · Fixed by #3140
Closed
Tracked by #2440

Introduce the notion of consensus backend mode #3116

kostko opened this issue Jul 19, 2020 · 0 comments · Fixed by #3140
Labels
c:breaking/cfg Category: breaks configuration c:consensus/cometbft Category: CometBFT

Comments

@kostko
Copy link
Member

kostko commented Jul 19, 2020 •
edited
Loading

The consensus backend should have a notion of a "mode" (configured via the --consensus.tendermint.mode flag) which should support the following options:

  • full runs a regular full consensus node (default),
  • (once implemented) light runs a light client consensus node (see Light consensus client/node #2440),
  • seed runs a seed-only consensus node (replaces the --tendermint.p2p.seed_mode).
@kostko kostko added c:consensus/cometbft Category: CometBFT c:breaking/cfg Category: breaks configuration labels Jul 19, 2020
@kostko kostko mentioned this issue Jul 19, 2020
Closed
9 tasks
@kostko kostko mentioned this issue Jul 29, 2020
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
c:breaking/cfg Category: breaks configuration c:consensus/cometbft Category: CometBFT
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Add consensus backend mode oasisprotocol/oasis-core
1 participant
@kostko