This repository has been archived by the owner on Nov 15, 2023. It is now read-only.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Disputes runtime #2947
Disputes runtime #2947
Changes from 1 commit
8bd80d3
101fde9
4198797
7dac193
dd01c06
ef153dc
8dea7e6
f70f6e2
0451139
6748578
95d6c19
ce5906b
01e948e
8e25b48
271434b
310ee52
37c3c3a
8180eae
2ed7fe5
31c27c0
cfdbebd
dcd410c
ebd8b18
da2d43a
d09c851
cfe3241
d14e904
7ffe889
3638877
82e86da
955e0c4
83e7b62
fc3ab87
6fa374c
1b4838d
c0d15be
7ef44b5
7570236
6dd0ad6
040cc17
4a3eeba
6f5b27f
aacc3de
993709b
5b7928a
14bd62d
776b3b6
a4ee80f
b0d579c
9430d3c
0680641
a715d61
3f6ce32
8ebc635
f3e22c0
53e2ccb
4f4b84b
a7ad191
7b04be6
c6cf3f7
3acf2c1
9aa95b4
ff06d0f
dd35e7f
df6bfa8
9214a99
eb81811
c7afa0c
4378b5c
8a7abdb
663b5cc
3be97bb
bb47ed4
5ecf237
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe I read it somewhere, but forgot. What do we do on timeout? Governance intervention, roll back just to be sure?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since one can not say for sure what should be done (that was the point of the dispute votes in the first place), so do nothing and let governance decide the action.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We'll slash everyone who should've participated in availability a tiny amount. Interestingly, if we worried about disputes spam slots preventing real disputes, then we'll want correlated timeouts to increase up to 100%, but..
Afaik, If we're confident the disputes spam slots blocking cannot obstruct real disputes: We do not care if adversarial nodes consume all their disputes spam slots. If honest parties votes in a dispute, then we should slash someone adversarial. If we've fill an honest nodes's disputes spam slot then we've so many of these the adversary should be slashed 100% by giving correlated wrong invalid votes.
We'd ideally spell this reasoning out more clearly elsewhere I guess, but so far I felt Rob's spam design aligns nicely.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If a dispute times out, it means that the nodes are unable to participate and recover availability. A dispute initiation is a claim that the data is available, so we apply a minor punishment to all nodes which participated in the dispute.