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

Figure out a secure way to exclude a validator from a committee round if they are unresponsive, temporarily until they are responsivel again #713

Open
stringhandler opened this issue Oct 2, 2023 · 1 comment
Open

Figure out a secure way to exclude a validator from a committee round if they are unresponsive, temporarily until they are responsivel again #713

stringhandler opened this issue Oct 2, 2023 · 1 comment

Comments

@stringhandler
Copy link
Contributor

stringhandler commented Oct 2, 2023 •
edited

originally logged by @sdbondi

NOTE: For the sake of simplicity, we could just live with this for now. Just noting it down as an issue.

If a validator is down (offline, catching up on blocks, DoS) the blocktime is severely delayed each time it comes around.

If a validator is offline for an extended period or indefinitely, this will happen until their registration expires. Currently, this is at most 100 epochs ~ 33 hours (1000 blocks).

We may want a leader failure mechanism where notes vote to exclude a peer for one or more subsequent rounds.
@stringhandler
Copy link
Contributor Author

agree with this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
Tari Digital Assets Network (DAN) backlog
Status: Not ready
Milestone
No milestone
Development

No branches or pull requests
1 participant
@stringhandler