Backport: process epoch changes and events every time a block is executed (#4799) #4810
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ra-io#4799) We would only process epoch changes and event streams when explicitly processing the inbox, which means it was possible eg. for users to unintentionally skip epoch updates while keeping proposing blocks on their chains. Process epoch changes (and any other relevant event streams) every time a block is proposed. CI - These changes should be backported to the latest `testnet` branch, then - be released in a new SDK, - [reviewer checklist](https://github.com/linera-io/linera-protocol/blob/main/CONTRIBUTING.md#reviewer-checklist)
deuszx
approved these changes
Oct 17, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
We would only process epoch changes and event streams when explicitly processing the inbox, which means it was possible eg. for users to unintentionally skip epoch updates while keeping proposing blocks on their chains.
Proposal
Process epoch changes (and any other relevant event streams) every time a block is proposed.
(Backport of #4799)
Test Plan
CI
Release Plan
Links