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

Consider persisting last round results in consensus state #4316

Closed
kostko opened this issue Oct 20, 2021 · 0 comments · Fixed by #4408
Closed

Consider persisting last round results in consensus state #4316

kostko opened this issue Oct 20, 2021 · 0 comments · Fixed by #4408
Assignees
@kostko
Labels
c:breaking/consensus Category: breaking consensus changes c:roothash Category: root hash service c:runtime Category: runtime

Comments

@kostko
Copy link
Member

kostko commented Oct 20, 2021

Currently last round results require access to historic consensus layer state (e.g. the block at the LastNormalHeight) which can prevent executors that use consensus state sync from processing blocks until they observe the next normal block.
@kostko kostko added c:roothash Category: root hash service c:runtime Category: runtime c:breaking/consensus Category: breaking consensus changes labels Oct 20, 2021
@kostko kostko self-assigned this Dec 22, 2021
@kostko kostko mentioned this issue Dec 22, 2021
Merged
@kostko kostko linked a pull request Dec 22, 2021 that will close this issue
go/roothash: Persist last round results in consensus state #4408
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@kostko kostko

Labels
c:breaking/consensus Category: breaking consensus changes c:roothash Category: root hash service c:runtime Category: runtime
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

go/roothash: Persist last round results in consensus state oasisprotocol/oasis-core
1 participant
@kostko