Currently, msgs signer validation is not performed when dispatching msgs of MsgExcute.
This leads to serious problems such as fraudulent transfers.
This can be prevented by making sure that the signer of the msg executed when dispatching msg is the signer of MsgExcute.
We will have to discuss later whether this modification is sufficient.
Description
Currently, msgs signer validation is not performed when dispatching msgs of MsgExcute. This leads to serious problems such as fraudulent transfers.
This can be prevented by making sure that the signer of the msg executed when dispatching msg is the signer of MsgExcute. We will have to discuss later whether this modification is sufficient.
Motivation and context
How has this been tested?
Screenshots (if appropriate):
Checklist:
CHANGELOG.md
client/docs/swagger-ui/swagger.yaml