-
Notifications
You must be signed in to change notification settings - Fork 1
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
fix: request id validation #51
Conversation
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.
TOB-WOND-4
explicitly mentions that the dispute's requestId
validation issue could be found within BondEscalationResolutionModule
, BondEscalationModule
, PrivateERC20ResolutionModule
and ERC20ResolutionModule
. However, I was able to detect the lack of the same recommended check around many other modules. Should this be a concern?
Besides, other similar validations are also extendedly absent, such as comparing with the response's requestId
or the dispute's responseId
. Again, should this be a concern?
@@ -53,6 +53,11 @@ interface IERC20ResolutionModule is IResolutionModule { | |||
*/ | |||
error ERC20ResolutionModule_OnlyDisputeModule(); |
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.
This custom error is not being used anywhere. 🙄
5f7ab67
to
9796e99
Compare
It should not. This is due to every function lacking
It should not be it outside of the warned modules, for the same reason; within the warned modules, there was one case where a |
🤖 Linear
Closes GRT-3