-
Notifications
You must be signed in to change notification settings - Fork 625
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
Move non-verification misbehaviour checks to CheckForMisbehaviour #2007
Comments
Hello, I would like to start working on this issue. Thank you! |
@Daniyal98 are you still working on this? |
@charleenfei It wasn't assigned to me so I didn't start working on it |
sorry about that! i am assigning you now :) |
Apologies for the delayed reply @Daniyal98. Will you be able to work on this issue now, or is it not the right time to pickup the issue? This issue is apart of our next iteration (Nov 28 - Dec 11) and we would like to complete it soon |
@colin-axner yeah sure. I will try my best :) |
@colin-axner the statement of this issue seems a bit misleading. The part that you mentioned is already in CheckForMisbehaviour. Am I missing something? |
Hi @Daniyal98 apologies again for the late reply! When I made the issue, I linked to main, but the code got moved around. The part of the code that should be moved is here, it should be moved into the switch statement case The idea is that when we check for misbehaviour, we have three cases to check for:
Since |
@Daniyal98 will you have time to work on this one relatively soon? No worries if you can't, but please let us know, so that we can take it otherwise. Thanks! |
Yes sure. I'll start working on it right away. |
Much appreciated, @Daniyal98! |
Summary
In 07-tendermint, we are checking whether something is misbehaviour in
VerifyClientMessage
, we should instead be doing this inCheckForMisbehaviour
. Move this batch of code to `CheckForMisbehaviourFor Admin Use
The text was updated successfully, but these errors were encountered: