-
Notifications
You must be signed in to change notification settings - Fork 136
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
Address race conditions in ICS misbehaviour handling #1147
Comments
sainoe
changed the title
Address the race condition in ICS misbehaviour
Address the race condition in ICS misbehaviour handling
Jul 14, 2023
sainoe
changed the title
Address the race condition in ICS misbehaviour handling
Address the race condition in the ICS misbehaviour handling
Jul 14, 2023
sainoe
changed the title
Address the race condition in the ICS misbehaviour handling
Address race conditions in the ICS misbehaviour handling
Jul 14, 2023
20 tasks
sainoe
changed the title
Address race conditions in the ICS misbehaviour handling
Address race conditions in ICS misbehaviour handling
Jul 14, 2023
20 tasks
21 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem
In the event of a IBC light client attack on the consumer, the associated client hosted on the provider can get frozen due to either the reception of an ICS misbehaviour message or a canonical IBC misbehaviour message. However, this creates a race condition that could cause the ICS misbehavior handling to fail. As a result, the byzantine validators responsible for the light client attack may not be adequately jailed as intended.
Closing criteria
Remove the ICS misbehavior handling logic updating the IBC client status
The text was updated successfully, but these errors were encountered: