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

[Improvement] A better way for plugins to use the account's native token balance #15

Open
adam-alchemy opened this issue Dec 1, 2023 · 0 comments

Comments

@adam-alchemy
Copy link

  • Right now the only configuration ability we give plugins to decide whether or not they should have permission to spend the account’s native token amount is via the manifest field canSpendNativeToken. This helps somewhat, but there may be some other plugin features that could benefit from “pulling” native tokens from the account address to the plugin address, or by “pushing” native tokens in the fallback itself.
    • Due to the current restriction that execute/executeBatch/executeFromPluginExternal cannot send to plugins, the native token amount cannot go directly to the calling plugin.
  • We should investigate whether this use case makes sense to include into the standard’s design, and if so, how to go about doing it.
@jaypaik jaypaik changed the title [Improvement] A better way for plugins to use the acocunt's native token balance [Improvement] A better way for plugins to use the account's native token balance Dec 5, 2023
@jaypaik jaypaik added this to the Simplify PluginManifest milestone Apr 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: No status
Development

No branches or pull requests

2 participants