-
Notifications
You must be signed in to change notification settings - Fork 25
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
[3/n permissions] feat: add execute user operation #77
Conversation
8c35ead
to
c4fa5d4
Compare
c4fa5d4
to
990a842
Compare
@@ -51,6 +54,26 @@ abstract contract PluginManager2 { | |||
} | |||
} | |||
|
|||
if (permissionHooks.length > 0) { |
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.
The name is growing on me. : )
In case we are doing the UO flow without UO context, aren't we skipping all permission hooks currently? Permission hooks currently get only invoked in The information on this would however only be available in UO validation and not in execution. Should we forward this info somehow? It seems tricky to do permission hooks in this case. |
8b7aa5a
to
ce2330e
Compare
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.
Looks good, just have 1 clarifying question.
changes:
executeUserOp
in UO validationabi.encode(PackedUserOperation)
if UO context is required, else sendabi.encodePacked(msg.sender, msg.value, msg.data)
installValidation
anduninstallValidation