Improvement: Standardized Context Management for ERC-7715 Permissions

[Smartdevs17]

While implementing ERC-7715 permissions in EnvioPilot, we found that managing the permissionsContext between the initial request and the subsequent redemption (often in different parts of the app or different sessions) requires custom state management.

It would be beneficial if the smart-accounts-kit provided:

A hook or utility to persist and retrieve active permission contexts.
More granular error types for when a permission redemption fails due to limit exhaustion or expiry.
Impact: This would lower the barrier for developers to implement complex, long-running permissions and improve the overall developer experience.

[jeffsmale90]

Thanks for raising this @Smartdevs17 !

We've been thinking a lot about how to be support developers storing these permissions between granting them, and redeeming them.

I believe that there's two cases; user-present transactions (e.g.., gaming, high frequency operations), and user-absent transactions (e.g., DCA, scheduled transactions, agentic operations).

For the first - where the user is present, but you don't necessarily want the user to be presented with a confirmation, we have added wallet_getGrantedExecutionPermissions to ERC-7715.

For the second - where the user isn't present, and a background service needs to be able to retrieve the permission, it's a little more complicated, as it necessitates infrastructure to store and manage these. We have experimented with various solutions for storing permissions for the developer, but as yet we do not have anything concrete to share.

Let me know if you have any specific details about your use case and needs that could help guide any potential improvements in this area.