You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
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.execute
/executeBatch
/executeFromPluginExternal
cannot send to plugins, the native token amount cannot go directly to the calling plugin.The text was updated successfully, but these errors were encountered: