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

Light consensus client/node #2440

Closed
8 of 9 tasks
kostko opened this issue Nov 28, 2019 · 0 comments
Closed
8 of 9 tasks

Light consensus client/node #2440

kostko opened this issue Nov 28, 2019 · 0 comments
Labels
c:consensus/cometbft Category: CometBFT c:performance Category: performance epic Epic (costed tracking issue)

Comments

@kostko
Copy link
Member

kostko commented Nov 28, 2019

We should support a light consensus client so that compute nodes which are not validators don't need to sync and execute everything.

Requires #1898 to make it easy to do remote consensus queries after verifying the headers and getting the state roots.

Related to #2349 to avoid compute nodes from doing irrelevant work.

Linked Issues

@kostko kostko added c:consensus/cometbft Category: CometBFT s:needs adr Needs a design document, discussion and decision (ADR) c:performance Category: performance labels Nov 28, 2019
@kostko kostko added the epic Epic (costed tracking issue) label May 5, 2020
@kostko kostko removed the s:needs adr Needs a design document, discussion and decision (ADR) label Jun 26, 2020
@kostko kostko changed the title Light consensus client Light consensus client/node Jun 26, 2020
@kostko kostko closed this as completed Feb 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c:consensus/cometbft Category: CometBFT c:performance Category: performance epic Epic (costed tracking issue)
Projects
None yet
Development

No branches or pull requests

1 participant