You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.
The Babe runtime module has the current_epoch() and next_epoch() functions that return the current and next epoch.
However these functions don't give any information about the configuration, which can potentially change between epochs (even though it never does in practice at the moment).
The configuration should either be added to the returned struct, or added a separate methods, or something like this.
Would be useful for GrandPa warp sync, in order to know about a configuration update that is pending at moment of the finalized block we sync to.
The text was updated successfully, but these errors were encountered:
The Babe runtime module has the
current_epoch()
andnext_epoch()
functions that return the current and next epoch.However these functions don't give any information about the configuration, which can potentially change between epochs (even though it never does in practice at the moment).
The configuration should either be added to the returned struct, or added a separate methods, or something like this.
Would be useful for GrandPa warp sync, in order to know about a configuration update that is pending at moment of the finalized block we sync to.
The text was updated successfully, but these errors were encountered: