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

Randomness DKG would stall epoch switch if one shard is completely offline #2121

Open
SkidanovAlex opened this issue Feb 11, 2020 · 2 comments
Assignees
Labels
A-chain Area: Chain, client & related
Milestone

Comments

@SkidanovAlex
Copy link
Collaborator

SkidanovAlex commented Feb 11, 2020

Currently the aggregate phase would stall if at least one shard is completely offline.

The solution should be to detect it happened (e.g. by observing that the aggregation phase didn't make progress for some number of steps), and to remove all the shares committed in the stalled shard from the aggregation (and to restart the aggregation).

@SkidanovAlex SkidanovAlex added the A-chain Area: Chain, client & related label Feb 11, 2020
@SkidanovAlex SkidanovAlex added this to the MainNet milestone Feb 11, 2020
@SkidanovAlex SkidanovAlex self-assigned this Feb 11, 2020
@SkidanovAlex SkidanovAlex modified the milestones: MainNet, Post MainNet Mar 4, 2020
@stale
Copy link

stale bot commented Jul 1, 2021

This issue has been automatically marked as stale because it has not had recent activity in the last 2 months.
It will be closed in 7 days if no further activity occurs.
Thank you for your contributions.

@stale stale bot added the S-stale label Jul 1, 2021
@bowenwang1996
Copy link
Collaborator

Randomness beacon near/NEPs#206

@stale stale bot removed the S-stale label Jul 1, 2021
@akhi3030 akhi3030 removed the S-pinned label Nov 28, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-chain Area: Chain, client & related
Projects
None yet
Development

No branches or pull requests

3 participants