You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.
We need information about disputes to propagate between nodes quickly - as soon as a validator observes a dispute, that information should propagate to others. As validators begin to participate in the dispute, those votes should also propagate through the network quickly. Disputes are rare and this protocol should probably be a flood-style protocol.
That said, there are a few spam/garbage vectors we'd like to mitigate:
2 colluding malicious validators can create an infinite amount of disputes where they contradict each other. This garbage should be avoided to keep the network free for legitimate traffic
Ancient disputes, which have no relevance, should not be re-broadcasted.
potentially others
The text was updated successfully, but these errors were encountered:
We need information about disputes to propagate between nodes quickly - as soon as a validator observes a dispute, that information should propagate to others. As validators begin to participate in the dispute, those votes should also propagate through the network quickly. Disputes are rare and this protocol should probably be a flood-style protocol.
That said, there are a few spam/garbage vectors we'd like to mitigate:
The text was updated successfully, but these errors were encountered: