-
Notifications
You must be signed in to change notification settings - Fork 150
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.
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
ADR: equivocation gov proposal #711
Conversation
Thanks for the contribution! Could you change the relevant ADR number instances from 2 -> 3, as I've just opened this PR for a feature that was merged a couple months ago. Probably best to keep things in the order they were merged |
Adds a new ADR related to the addition of the equivocation gov proposal, and the disabling of the consumer initiated slashing. Co-authored-by: Albert Le Batteux <contact@albttx.tech>
6661116
to
01d98d7
Compare
Done! |
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.
LGTM thanks!
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.
IIUC we can inspect IBC releated events on the provider to confirm that an equivocation slash packet was accepted by the provider. The packet is dropped, but the event about it being received will remain.
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.
LGTM
Description
Adds a new ADR related to the addition of the equivocation gov proposal, and the disabling of the consumer initiated slashing.
Since the PR that implements the new gov proposal is merged, I considered the status of this ADR
accepted
.Type of change
Docs
: Adds documentation