This repository has been archived by the owner on Jan 13, 2025. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 4.5k
Mitigate attacks that cause a node to reach finality #8616
Labels
stale
[bot only] Added to stale content; results in auto-close after a week.
Milestone
Comments
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
bot
added
the
stale
[bot only] Added to stale content; results in auto-close after a week.
label
Apr 19, 2021
This stale issue has been automatically closed. Thank you for your contributions. |
This was referenced Apr 13, 2023
This was referenced Apr 15, 2023
This was referenced Apr 15, 2023
Open
Open
This was referenced Apr 18, 2023
Open
Open
This was referenced May 23, 2023
Open
Open
This was referenced May 29, 2023
Open
Open
This was referenced May 31, 2023
Open
This was referenced Jun 3, 2023
This was referenced Jun 3, 2023
Open
This was referenced Jun 5, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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:
Proposal:
tag: @carllin @mvines
The text was updated successfully, but these errors were encountered: