Skip to content
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

Implement misbehavior monitoring and evidence relaying #632

Closed
5 tasks
ancazamfir opened this issue Feb 10, 2021 · 0 comments · Fixed by #691
Closed
5 tasks

Implement misbehavior monitoring and evidence relaying #632

ancazamfir opened this issue Feb 10, 2021 · 0 comments · Fixed by #691
Assignees
Labels
I: logic Internal: related to the relaying logic O: security Objective: cause to enhance security and improve safety
Milestone

Comments

@ancazamfir
Copy link
Collaborator

ancazamfir commented Feb 10, 2021

Crate

relayer, relayer-cli, modules

Summary

Add a new capability for the relayer to monitor IBC client updates, conflicting headers and submit proof of misbehavior in MsgSubmitMisbehaviour transaction.

Problem Definition

Proposal

(details will be added soon)


For Admin Use

  • Not duplicate issue
  • Appropriate labels applied
  • Appropriate milestone (priority) applied
  • Appropriate contributors tagged
  • Contributor assigned/self-assigned
@ancazamfir ancazamfir added this to the v0.1.2 milestone Feb 10, 2021
@ancazamfir ancazamfir self-assigned this Feb 12, 2021
@adizere adizere modified the milestones: backlog, 03.2021 Mar 9, 2021
@adizere adizere added I: logic Internal: related to the relaying logic O: security Objective: cause to enhance security and improve safety labels Mar 9, 2021
@romac romac mentioned this issue Mar 30, 2021
5 tasks
@romac romac closed this as completed in #691 Apr 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
I: logic Internal: related to the relaying logic O: security Objective: cause to enhance security and improve safety
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants