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

Genesis validators incorrect when min genesis time in future #4370

Closed
prestonvanloon opened this issue Dec 29, 2019 · 2 comments · Fixed by #4373
Closed

Genesis validators incorrect when min genesis time in future #4370

prestonvanloon opened this issue Dec 29, 2019 · 2 comments · Fixed by #4373
Assignees
Labels
Bug Something isn't working Priority: Critical Highest, immediate priority item

Comments

@prestonvanloon
Copy link
Member

prestonvanloon commented Dec 29, 2019

Problem scenario:

  • Send more than MinGenesisActiveValidatorCount valid deposits before MinGenesisTime.
  • When current time exceeds MinGenesisTime, all valid deposits are added to the genesis state.
  • New nodes that sync after genesis time have only MinGenesisActiveValidatorCount validators.

Expected behavior:

  • Same behavior as pre-genesis nodes.

Edit: Edited to update based on feedback from @nisdas.

@prestonvanloon
Copy link
Member Author

Re-opening. I believe there is still an issue here. From my observation, if the number of genesis validators is not exactly the min amount then there are problems for new nodes to sync to the network after the chain has started.

@prestonvanloon
Copy link
Member Author

This should be resolved in v0.9.2 from #4329

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working Priority: Critical Highest, immediate priority item
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants