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

IF: Use actual active_finalizer_policy_generation in finality_data #2352

Closed
linh2931 opened this issue Mar 28, 2024 · 0 comments · Fixed by #2358
Closed

IF: Use actual active_finalizer_policy_generation in finality_data #2352

linh2931 opened this issue Mar 28, 2024 · 0 comments · Fixed by #2358
Assignees
@linh2931
Labels
👍 lgtm
Milestone
Instant Finality:...

Comments

@linh2931
Copy link
Member

When finalizer policy change is implemented, please use actual active_finalizer_policy_generation when constructing finality_data.
This was referenced Mar 28, 2024
Merged
Merged
@linh2931 linh2931 self-assigned this Mar 29, 2024
@linh2931 linh2931 added 👍 lgtm and removed triage labels Mar 29, 2024
@linh2931 linh2931 added this to the Instant Finality: Cusp milestone Mar 29, 2024
@linh2931 linh2931 linked a pull request Mar 29, 2024 that will close this issue
IF: set active finalizer policy generation in finality_data for SHiP correctly #2358
Merged
@arhag arhag closed this as completed Apr 1, 2024
@arhag arhag modified the milestones: Instant Finality: Cusp, Instant Finality: Production-Ready Apr 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@linh2931 linh2931

Labels
👍 lgtm
Projects
Team Backlog
Archived in project
Milestone
Instant Finality: Production-Ready
Development

Successfully merging a pull request may close this issue.

IF: set active finalizer policy generation in finality_data for SHiP correctly AntelopeIO/leap
3 participants
@arhag @linh2931 @enf-ci-bot