Skip to content
This repository has been archived by the owner on Jan 13, 2025. It is now read-only.

Mitigate attacks that cause a node to reach finality #8616

Closed
aeyakovenko opened this issue Mar 4, 2020 · 2 comments
Closed

Mitigate attacks that cause a node to reach finality #8616

aeyakovenko opened this issue Mar 4, 2020 · 2 comments
Labels
stale [bot only] Added to stale content; results in auto-close after a week.
Milestone

Comments

@aeyakovenko
Copy link
Member

aeyakovenko commented Mar 4, 2020

Problem

We want to make sure that nodes do not reach full confirmation on any blocks that the supermajority doesn't have agreement on. This is a property of consensus, but we need some mechanism to double check it during runtime.

Proposed Solution

Ideas:

  • Monitor the votes in gossip and halt if the supermajority is not on the same fork as BankForks

Proposal:

  1. Add current root to EpochSlots
  2. when collecting epoch slots assert that root is either a parent of the current root, a child of the current root, or unknown.
  3. if the check fails for a superminority of roots, halt the node.

tag: @carllin @mvines

@mvines mvines added this to the The Future! milestone Apr 19, 2020
@stale
Copy link

stale bot commented Apr 19, 2021

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

@stale stale bot added the stale [bot only] Added to stale content; results in auto-close after a week. label Apr 19, 2021
@stale
Copy link

stale bot commented Jun 3, 2021

This stale issue has been automatically closed. Thank you for your contributions.

@stale stale bot closed this as completed Jun 3, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
stale [bot only] Added to stale content; results in auto-close after a week.
Projects
None yet
Development

No branches or pull requests

2 participants