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

Hard Forks and Optimistic Conf #10275

Open
aeyakovenko opened this issue May 27, 2020 · 0 comments
Open

Hard Forks and Optimistic Conf #10275

aeyakovenko opened this issue May 27, 2020 · 0 comments
Milestone

Comments

@aeyakovenko
Copy link
Member

aeyakovenko commented May 27, 2020

Problem

Hard Forks are going to be hard.

  1. Abandonded blocks after the hardfork may have votes

Proposed Solution

  1. Votes after the optimistic block need to be ignored for optimistic configuration after restart.
  2. after snapshot is enabled, we should set a --min-optimistic-slot=X, where X is the root slot where the clients should start accepting new optimistic blocks. Until that point full finality needs to be reached. Maybe it's easier to do it in the next epoch

tag: @carllin

@mvines mvines added this to the v1.4.0 milestone Aug 18, 2020
@mvines mvines modified the milestones: v1.4.0, v1.5.0 Oct 8, 2020
@mvines mvines modified the milestones: v1.5.0, v1.6.0 Dec 17, 2020
@mvines mvines modified the milestones: v1.6.0, v1.7.0 Mar 11, 2021
@mvines mvines modified the milestones: v1.7.0, v1.8.0 May 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants