Skip to content
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

feat: allow approval based paymasters #251

Merged
merged 8 commits into from
Jan 13, 2025

Conversation

ly0va
Copy link
Member

@ly0va ly0va commented Jan 10, 2025

Description

Allow approval-based paymaster, while performing the necessary check that the used token is allowed in the session spec.

Copy link
Contributor

@cpb8010 cpb8010 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The tests make this digestible!

@ly0va ly0va enabled auto-merge (squash) January 13, 2025 09:13
@ly0va ly0va merged commit 255a301 into main Jan 13, 2025
3 checks passed
@ly0va ly0va deleted the lyova-allow-approval-based-paymasters branch January 13, 2025 09:14
@@ -93,7 +93,6 @@ contract SessionKeyValidator is IModuleValidator {
interfaceId == type(IModule).interfaceId;
}

// TODO: make the session owner able revoke its own key, in case it was leaked, to prevent further misuse?
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Are we not implementing this?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you think we should? I think it's a feature that is very unlikely to be used, but adds complexity

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is a nice to have. However, it is true that a key compromise will already have a much larger impact than the session itself.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants