diff --git a/ERCS/erc-1328.md b/ERCS/erc-1328.md index 262217bbb4..94f0a374ed 100644 --- a/ERCS/erc-1328.md +++ b/ERCS/erc-1328.md @@ -4,7 +4,8 @@ title: WalletConnect URI Format description: Define URI format for initiating connections between applications and wallets author: ligi (@ligi), Pedro Gomes (@pedrouid) discussions-to: https://ethereum-magicians.org/t/wallet-connect-eip/850 -status: Review +status: Last Call +last-call-deadline: 2024-02-07 type: Standards Track category: ERC created: 2018-08-15 diff --git a/ERCS/erc-6900.md b/ERCS/erc-6900.md index dee85d1f10..9f9de2ceeb 100644 --- a/ERCS/erc-6900.md +++ b/ERCS/erc-6900.md @@ -77,7 +77,7 @@ A call to the smart contract account can be broken down into the steps as shown The following diagram shows permitted plugin execution flows. During a plugin's execution step from the above diagram, the plugin may perform a "Plugin Execution Function", using either `executeFromPlugin` or `executeFromPluginExternal`. These can be used by plugins to execute using the account's context. - `executeFromPlugin` handles calls to other installed plugin's execution function on the modular account. -- `executeFromPluginExternal` handles calls to external contracts. +- `executeFromPluginExternal` handles calls to external addresses. ![diagram showing a plugin execution flow](../assets/eip-6900/Plugin_Execution_Flow.svg) @@ -87,7 +87,7 @@ Each step is modular, supporting different implementations for each execution fu **Modular Smart Contract Accounts** **MUST** implement -- `IAccount` from [ERC-4337](./eip-4337.md). +- `IAccount.sol` from [ERC-4337](./eip-4337.md). - `IPluginManager.sol` to support installing and uninstalling plugins. - `IStandardExecutor.sol` to support open-ended execution. **Calls to plugins through this SHOULD revert.** - `IPluginExecutor.sol` to support execution from plugins. **Calls to plugins through `executeFromPluginExternal` SHOULD revert.** @@ -98,53 +98,33 @@ Each step is modular, supporting different implementations for each execution fu **Plugins** **MUST** implement -- `IPlugin` interface described below and implement [ERC-165](./eip-165.md) for `IPlugin`. +- `IPlugin.sol` described below and implement [ERC-165](./eip-165.md) for `IPlugin`. #### `IPluginManager.sol` Plugin manager interface. Modular Smart Contract Accounts **MUST** implement this interface to support installing and uninstalling plugins. ```solidity -interface IPluginManager { - // Pre/post exec hooks added by the user to limit the scope a plugin has - // These hooks are injected at plugin install time - struct InjectedHook { - // The plugin that provides the hook - address providingPlugin; - // Either a plugin-defined execution function, or the native function executeFromPluginExternal - bytes4 selector; - InjectedHooksInfo injectedHooksInfo; - bytes hookApplyData; - } - - struct InjectedHooksInfo { - uint8 preExecHookFunctionId; - bool isPostHookUsed; - uint8 postExecHookFunctionId; - } +// Treats the first 20 bytes as an address, and the last byte as a function identifier. +type FunctionReference is bytes21; - event PluginInstalled( - address indexed plugin, - bytes32 manifestHash, - FunctionReference[] dependencies, - InjectedHook[] injectedHooks - ); +interface IPluginManager { + event PluginInstalled(address indexed plugin, bytes32 manifestHash, FunctionReference[] dependencies); - event PluginUninstalled(address indexed plugin, bool indexed callbacksSucceeded); + event PluginUninstalled(address indexed plugin, bool indexed onUninstallSucceeded); /// @notice Install a plugin to the modular account. /// @param plugin The plugin to install. /// @param manifestHash The hash of the plugin manifest. - /// @param pluginInitData Optional data to be decoded and used by the plugin to setup initial plugin data for - /// the modular account. - /// @param dependencies The dependencies of the plugin, as described in the manifest. - /// @param injectedHooks Optional hooks to be injected over permitted calls this plugin may make. + /// @param pluginInstallData Optional data to be decoded and used by the plugin to setup initial plugin data + /// for the modular account. + /// @param dependencies The dependencies of the plugin, as described in the manifest. Each FunctionReference + /// MUST be composed of an installed plugin's address and a function ID of its validation function. function installPlugin( address plugin, bytes32 manifestHash, - bytes calldata pluginInitData, - FunctionReference[] calldata dependencies, - InjectedHook[] calldata injectedHooks + bytes calldata pluginInstallData, + FunctionReference[] calldata dependencies ) external; /// @notice Uninstall a plugin from the modular account. @@ -153,14 +133,7 @@ interface IPluginManager { /// guarantees. /// @param pluginUninstallData Optional data to be decoded and used by the plugin to clear plugin data for the /// modular account. - /// @param hookUnapplyData Optional data to be decoded and used by the plugin to clear injected hooks for the - /// modular account. - function uninstallPlugin( - address plugin, - bytes calldata config, - bytes calldata pluginUninstallData, - bytes[] calldata hookUnapplyData - ) external; + function uninstallPlugin(address plugin, bytes calldata config, bytes calldata pluginUninstallData) external; } ``` @@ -175,25 +148,26 @@ Standard execute functions SHOULD check whether the call's target implements the ```solidity struct Call { - // The target contract for account to execute. + // The target address for the account to call. address target; - // The value for the call. + // The value to send with the call. uint256 value; - // The call data for the call. + // The calldata for the call. bytes data; } interface IStandardExecutor { /// @notice Standard execute method. /// @dev If the target is a plugin, the call SHOULD revert. - /// @param target The target contract for account to execute. - /// @param value The value for the call. - /// @param data The call data for the call. + /// @param target The target address for account to call. + /// @param value The value to send with the call. + /// @param data The calldata for the call. /// @return The return data from the call. function execute(address target, uint256 value, bytes calldata data) external payable returns (bytes memory); /// @notice Standard executeBatch method. - /// @dev If the target is a plugin, the call SHOULD revert. + /// @dev If the target is a plugin, the call SHOULD revert. If any of the calls revert, the entire batch MUST + /// revert. /// @param calls The array of calls. /// @return An array containing the return data from the calls. function executeBatch(Call[] calldata calls) external payable returns (bytes[] memory); @@ -212,17 +186,23 @@ This prevents accidental misconfiguration or misuse of plugins (both installed a ```solidity interface IPluginExecutor { - /// @notice Method from calls made from plugins. - /// @param data The call data for the call. + /// @notice Execute a call from a plugin through the account. + /// @dev Permissions must be granted to the calling plugin for the call to go through. + /// @param data The calldata to send to the account. /// @return The return data from the call. function executeFromPlugin(bytes calldata data) external payable returns (bytes memory); - /// @notice Method from cals made from plugins. - /// @dev If the target is a plugin, the call SHOULD revert. - /// @param target The target of the external contract to be called. - /// @param value The value to pass. - /// @param data The data to pass. - function executeFromPluginExternal(address target, uint256 value, bytes calldata data) external payable; + /// @notice Execute a call from a plugin to a non-plugin address. + /// @dev If the target is a plugin, the call SHOULD revert. Permissions must be granted to the calling plugin + /// for the call to go through. + /// @param target The address to be called. + /// @param value The value to send with the call. + /// @param data The calldata to send to the target. + /// @return The return data from the call. + function executeFromPluginExternal(address target, uint256 value, bytes calldata data) + external + payable + returns (bytes memory); } ``` @@ -231,48 +211,36 @@ interface IPluginExecutor { Plugin inspection interface. Modular Smart Contract Accounts **MAY** implement this interface to support visibility in plugin configuration on-chain. ```solidity -// Treats the first 20 bytes as an address, and the last byte as a function identifier. -type FunctionReference is bytes21; - interface IAccountLoupe { - /// @notice Config for an execution function, given a selector + /// @notice Config for an execution function, given a selector. struct ExecutionFunctionConfig { address plugin; FunctionReference userOpValidationFunction; FunctionReference runtimeValidationFunction; } - /// @notice Pre and post hooks for a given selector - /// @dev It's possible for one of either `preExecHook` or `postExecHook` to be empty + /// @notice Pre and post hooks for a given selector. + /// @dev It's possible for one of either `preExecHook` or `postExecHook` to be empty. struct ExecutionHooks { FunctionReference preExecHook; FunctionReference postExecHook; } - /// @notice Gets the validation functions and plugin address for a selector - /// @dev If the selector is a native function, the plugin address will be the address of the account - /// @param selector The selector to get the configuration for - /// @return The configuration for this selector + /// @notice Get the validation functions and plugin address for a selector. + /// @dev If the selector is a native function, the plugin address will be the address of the account. + /// @param selector The selector to get the configuration for. + /// @return The configuration for this selector. function getExecutionFunctionConfig(bytes4 selector) external view returns (ExecutionFunctionConfig memory); - /// @notice Gets the pre and post execution hooks for a selector - /// @param selector The selector to get the hooks for - /// @return The pre and post execution hooks for this selector + /// @notice Get the pre and post execution hooks for a selector. + /// @param selector The selector to get the hooks for. + /// @return The pre and post execution hooks for this selector. function getExecutionHooks(bytes4 selector) external view returns (ExecutionHooks[] memory); - /// @notice Gets the pre and post permitted call hooks applied for a plugin calling this selector - /// @param callingPlugin The plugin that is calling the selector - /// @param selector The selector the plugin is calling - /// @return The pre and post permitted call hooks for this selector - function getPermittedCallHooks(address callingPlugin, bytes4 selector) - external - view - returns (ExecutionHooks[] memory); - - /// @notice Gets the pre user op and runtime validation hooks associated with a selector - /// @param selector The selector to get the hooks for - /// @return preUserOpValidationHooks The pre user op validation hooks for this selector - /// @return preRuntimeValidationHooks The pre runtime validation hooks for this selector + /// @notice Get the pre user op and runtime validation hooks associated with a selector. + /// @param selector The selector to get the hooks for. + /// @return preUserOpValidationHooks The pre user op validation hooks for this selector. + /// @return preRuntimeValidationHooks The pre runtime validation hooks for this selector. function getPreValidationHooks(bytes4 selector) external view @@ -281,8 +249,8 @@ interface IAccountLoupe { FunctionReference[] memory preRuntimeValidationHooks ); - /// @notice Gets an array of all installed plugins - /// @return The addresses of all installed plugins + /// @notice Get an array of all installed plugins. + /// @return The addresses of all installed plugins. function getInstalledPlugins() external view returns (address[] memory); } ``` @@ -303,28 +271,6 @@ interface IPlugin { /// @param data Optional bytes array to be decoded and used by the plugin to clear plugin data for the modular account. function onUninstall(bytes calldata data) external; - /// @notice A hook that runs when a hook this plugin owns is installed onto another plugin - /// @dev Optional, use to implement any required setup logic - /// @param pluginAppliedOn The plugin that the hook is being applied on - /// @param injectedHooksInfo Contains pre/post exec hook information - /// @param data Any optional data for setup - function onHookApply( - address pluginAppliedOn, - IPluginManager.InjectedHooksInfo calldata injectedHooksInfo, - bytes calldata data - ) external; - - /// @notice A hook that runs when a hook this plugin owns is unapplied from another plugin - /// @dev Optional, use to implement any required unapplied logic - /// @param pluginAppliedOn The plugin that the hook was applied on - /// @param injectedHooksInfo Contains pre/post exec hook information - /// @param data Any optional data for the unapplied call - function onHookUnapply( - address pluginAppliedOn, - IPluginManager.InjectedHooksInfo calldata injectedHooksInfo, - bytes calldata data - ) external; - /// @notice Run the pre user operation validation hook specified by the `functionId`. /// @dev Pre user operation validation hooks MUST NOT return an authorizer value other than 0 or 1. /// @param functionId An identifier that routes the call to different internal implementations, should there be more than one. @@ -377,7 +323,7 @@ interface IPlugin { function postExecutionHook(uint8 functionId, bytes calldata preExecHookData) external; /// @notice Describe the contents and intended configuration of the plugin. - /// @dev The manifest MUST stay constant over time. + /// @dev This manifest MUST stay constant over time. /// @return A manifest describing the contents and intended configuration of the plugin. function pluginManifest() external pure returns (PluginManifest memory); @@ -394,27 +340,28 @@ The plugin manifest is responsible for describing the execution functions, valid ```solidity enum ManifestAssociatedFunctionType { - /// @notice Function is not defined. + // Function is not defined. NONE, - /// @notice Function belongs to this plugin. + // Function belongs to this plugin. SELF, - /// @notice Function belongs to an external plugin provided as a dependency during plugin installation. + // Function belongs to an external plugin provided as a dependency during plugin installation. Plugins MAY depend + // on external validation functions. It MUST NOT depend on external hooks, or installation will fail. DEPENDENCY, - /// @notice Resolves to a magic value to always bypass runtime validation for a given function. - /// This is only assignable on runtime validation functions. If it were to be used on a user op validationFunction, - /// it would risk burning gas from the account. When used as a hook in any hook location, it is equivalent to not - /// setting a hook and is therefore disallowed. + // Resolves to a magic value to always bypass runtime validation for a given function. + // This is only assignable on runtime validation functions. If it were to be used on a user op validationFunction, + // it would risk burning gas from the account. When used as a hook in any hook location, it is equivalent to not + // setting a hook and is therefore disallowed. RUNTIME_VALIDATION_ALWAYS_ALLOW, - /// @notice Resolves to a magic value to always fail in a hook for a given function. - /// This is only assignable to pre hooks (pre validation and pre execution). It should not be used on - /// validation functions themselves, because this is equivalent to leaving the validation functions unset. - /// It should not be used in post-exec hooks, because if it is known to always revert, that should happen - /// as early as possible to save gas. + // Resolves to a magic value to always fail in a hook for a given function. + // This is only assignable to pre hooks (pre validation and pre execution). It should not be used on + // validation functions themselves, because this is equivalent to leaving the validation functions unset. + // It should not be used in post-exec hooks, because if it is known to always revert, that should happen + // as early as possible to save gas. PRE_HOOK_ALWAYS_DENY } -// For functions of type `ManifestAssociatedFunctionType.DEPENDENCY`, the MSCA MUST find the plugin address -// of the function at `dependencies[dependencyIndex]` during the call to `installPlugin(config)`. +/// @dev For functions of type `ManifestAssociatedFunctionType.DEPENDENCY`, the MSCA MUST find the plugin address +/// of the function at `dependencies[dependencyIndex]` during the call to `installPlugin(config)`. struct ManifestFunction { ManifestAssociatedFunctionType functionType; uint8 functionId; @@ -452,26 +399,28 @@ struct PluginMetadata { // The author field SHOULD be a username representing the identity of the user or organization // that created this plugin. string author; - // String desciptions of the relative sensitivity of specific functions. The selectors MUST be selectors for + // String descriptions of the relative sensitivity of specific functions. The selectors MUST be selectors for // functions implemented by this plugin. SelectorPermission[] permissionDescriptors; } /// @dev A struct describing how the plugin should be installed on a modular account. struct PluginManifest { - // List of ERC-165 interfaceIds to add to account to support introspection checks. + // List of ERC-165 interface IDs to add to account to support introspection checks. This MUST NOT include + // IPlugin's interface ID. bytes4[] interfaceIds; - // If this plugin depends on other plugins' validation functions and/or hooks, the interface IDs of - // those plugins MUST be provided here, with its position in the array matching the `dependencyIndex` - // members of `ManifestFunction` structs used in the manifest. + // If this plugin depends on other plugins' validation functions, the interface IDs of those plugins MUST be + // provided here, with its position in the array matching the `dependencyIndex` members of `ManifestFunction` + // structs used in the manifest. bytes4[] dependencyInterfaceIds; // Execution functions defined in this plugin to be installed on the MSCA. bytes4[] executionFunctions; // Plugin execution functions already installed on the MSCA that this plugin will be able to call. bytes4[] permittedExecutionSelectors; - // Boolean to indicate whether the plugin can call any external contract addresses. + // Boolean to indicate whether the plugin can call any external address. bool permitAnyExternalAddress; - // Boolean to indicate whether the plugin needs access to spend native tokens of the account. + // Boolean to indicate whether the plugin needs access to spend native tokens of the account. If false, the + // plugin MUST still be able to spend up to the balance that it sends to the account in the same call. bool canSpendNativeToken; ManifestExternalCallPermission[] permittedExternalCalls; ManifestAssociatedFunction[] userOpValidationFunctions; @@ -479,7 +428,6 @@ struct PluginManifest { ManifestAssociatedFunction[] preUserOpValidationHooks; ManifestAssociatedFunction[] preRuntimeValidationHooks; ManifestExecutionHook[] executionHooks; - ManifestExecutionHook[] permittedCallHooks; } ``` @@ -488,11 +436,11 @@ struct PluginManifest { #### Responsibilties of `StandardExecutor` and `PluginExecutor` -`StandardExecutor` functions are mainly used for open-ended execution of external contracts. +`StandardExecutor` functions are used for open-ended calls to external addresses. `PluginExecutor` functions are specifically used by plugins to request the account to execute with account's context. Explicit permissions are required for plugins to use `PluginExecutor`. -The following behavior must be followed: +The following behavior MUST be followed: - `StandardExecutor` can NOT call plugin execution functions and/or `PluginExecutor`. This is guaranteed by checking whether the call's target implements the `IPlugin` interface via ERC-165 as required. - `StandardExecutor` can NOT be called by plugin execution functions and/or `PluginExecutor`. @@ -500,7 +448,7 @@ The following behavior must be followed: #### Calls to `installPlugin` -The function `installPlugin` accepts 5 parameters: the address of the plugin to install, the Keccak-256 hash of the plugin's manifest, ABI-encoded data to pass to the plugin's `onInstall` callback, an array of function references that represent the plugin's install dependencies, and permitted call hooks to apply during installation. +The function `installPlugin` accepts 4 parameters: the address of the plugin to install, the Keccak-256 hash of the plugin's manifest, ABI-encoded data to pass to the plugin's `onInstall` callback, and an array of function references that represent the plugin's install dependencies. The function MUST retrieve the plugin's manifest by calling `pluginManifest()` using `staticcall`. @@ -511,20 +459,20 @@ The function MUST perform the following preliminary checks: - Revert if `manifestHash` does not match the computed Keccak-256 hash of the plugin's returned manifest. This prevents installation of plugins that attempt to install a different plugin configuration than the one that was approved by the client. - Revert if any address in `dependencies` does not support the interface at its matching index in the manifest's `dependencyInterfaceIds`, or if the two array lengths do not match, or if any of the dependencies are not already installed on the modular account. -The function MUST record the manifest hash, dependencies, and permitted call hooks that were used for the plugin's installation. Each dependency's record MUST also be updated to reflect that it has a new dependent. These records MUST be used to ensure calls to `uninstallPlugin` are comprehensive and undo all editted configuration state from installation. The mechanism by which these records are stored and validated is up to the implementation. +The function MUST record the manifest hash and dependencies that were used for the plugin's installation. Each dependency's record MUST also be updated to reflect that it has a new dependent. These records MUST be used to ensure calls to `uninstallPlugin` are comprehensive and undo all edited configuration state from installation. The mechanism by which these records are stored and validated is up to the implementation. -The function MUST store the plugin's permitted function selectors and external contract calls to be able to validate calls to `executeFromPlugin` and `executeFromPluginExternal`. +The function MUST store the plugin's permitted function selectors, permitted external calls, and whether it can spend the account's native tokens, to be able to validate calls to `executeFromPlugin` and `executeFromPluginExternal`. The function MUST parse through the execution functions, validation functions, and hooks in the manifest and add them to the modular account after resolving each `ManifestFunction` type. -- Each function selector MUST be added as a valid execution function on the modular account. If the function selector has already been added or matches the selector of a native function, the function SHOULD revert. +- Each execution function selector MUST be added as a valid execution function on the modular account. If the function selector has already been added or matches the selector of a native function, the function SHOULD revert. - If a validation function is to be added to a selector that already has that type of validation function, the function SHOULD revert. -Next, the function MUST call the plugin's `onInstall` callback with the data provided in the `installData` parameter. This serves to initialize the plugin state for the modular account. If `onInstall` reverts, the `installPlugin` function MUST revert. +The function MAY store the interface IDs provided in the manifest's `interfaceIds` and update its `supportsInterface` behavior accordingly. -For each injected hook provided, the function MUST add the permitted call hook using the currently installing plugin as the caller and the provided function selector as the execution function selector. Then, the function MUST call onHookApply with the user-provided initialization data, if the data is nonempty. +Next, the function MUST call the plugin's `onInstall` callback with the data provided in the `pluginInstallData` parameter. This serves to initialize the plugin state for the modular account. If `onInstall` reverts, the `installPlugin` function MUST revert. -Finally, the function must emit the event `PluginInstalled` with the plugin's address and a hash of its manifest. +Finally, the function MUST emit the event `PluginInstalled` with the plugin's address, the hash of its manifest, and the dependencies that were used. > **⚠️ The ability to install and uninstall plugins is very powerful. The security of these functions determines the security of the account. It is critical for modular account implementers to make sure the implementation of the functions in `IPluginManager` have the proper security consideration and access control in place.** @@ -537,25 +485,27 @@ The function MUST revert if the plugin is not installed on the modular account. The function SHOULD perform the following checks: - Revert if the hash of the manifest used at install time does not match the computed Keccak-256 hash of the plugin's current manifest. This prevents unclean removal of plugins that attempt to force a removal of a different plugin configuration than the one that was originally approved by the client for installation. To allow for removal of such plugins, the modular account MAY implement the capability for the manifest to be encoded in the config field as a parameter. -- Revert if there is at least 1 other installed plugin that depends on validation functions or hooks added by this plugin. Plugins used as dependencies must not be uninstalled while dependent plugins exist. +- Revert if there is at least 1 other installed plugin that depends on validation functions added by this plugin. Plugins used as dependencies SHOULD NOT be uninstalled while dependent plugins exist. The function SHOULD update account storage to reflect the uninstall via inspection functions, such as those defined by `IAccountLoupe`. Each dependency's record SHOULD also be updated to reflect that it has no longer has this plugin as a dependent. -The function MUST remove records for the plugin's dependencies, injected permitted call hooks, permitted function selectors, and permitted external calls. The hooks to remove MUST be exactly the same as what was provided during installation. It is up to the implementing modular account to decide how to keep this invariant. The config parameter field MAY be used. +The function MUST remove records for the plugin's manifest hash, dependencies, permitted function selectors, permitted external calls, and whether it can spend the account's native tokens. + +The function MUST parse through the execution functions, validation functions, and hooks in the manifest and remove them from the modular account after resolving each `ManifestFunction` type. If multiple plugins added the same hook, it MUST persist until the last plugin is uninstalled. -The function MUST parse through the execution functions, validation functions, and hooks in the manifest and remove them from the modular account after resolving each `ManifestFunction` type. +If the account stored the interface IDs provided in the manifest's `interfaceIds` during installation, it MUST remove them and update its `supportsInterface` behavior accordingly. If multiple plugins added the same interface ID, it MUST persist until the last plugin is uninstalled. -Next, for each previously injected hook, the function MUST remove the permitted call hook using the currently uninstalling plugin as the caller and the provided function selector as the execution function selector. Then, the function MUST call onHookUnapply with the user-provided initialization data, if the data is nonempty. +Next, the function MUST call the plugin's `onUninstall` callback with the data provided in the `pluginUninstallData` parameter. This serves to clear the plugin state for the modular account. If `onUninstall` reverts, execution SHOULD continue to allow the uninstall to complete. -Finally, the function MUST call the plugin's `onUninstall` callback with the data provided in the `uninstallData` parameter. This serves to clear the plugin state for the modular account. If `onUninstall` reverts, execution SHOULD continue to allow the uninstall to complete. +Finally, the function MUST emit the event `PluginUninstalled` with the plugin's address and whether the `onUninstall` callback succeeded. -> **⚠️ Incorrectly uninstalled plugins can prevent uninstallation of their dependencies. Therefore, some form of validation that the uninstall step completely and correctly removes the plugin and its usage of dependencies is required.** +> **⚠️ Incorrectly uninstalled plugins can prevent uninstalls of their dependencies. Therefore, some form of validation that the uninstall step completely and correctly removes the plugin and its usage of dependencies is required.** #### Calls to `validateUserOp` When the function `validateUserOp` is called on modular account by the `EntryPoint`, it MUST find the user operation validation function associated to the function selector in the first four bytes of `userOp.callData`. If there is no function defined for the selector, or if `userOp.callData.length < 4`, then execution MUST revert. -If the function selector has associated pre user operation validation hooks, then those hooks MUST be run sequentially. If any revert, the outer call MUST revert. If any are set to `PRE_HOOK_ALWAYS_DENY`, the call must revert. If any return an `authorizer` value other than 0 or 1, execution MUST revert. If any return an `authorizer` value of 1, indicating an invalid signature, the returned validation data of the outer call MUST also be 1. If any return time-bounded validation by specifying either a `validUntil` or `validBefore` value, the resulting validation data MUST be the intersection of all time bounds provided. +If the function selector has associated pre user operation validation hooks, then those hooks MUST be run sequentially. If any revert, the outer call MUST revert. If any are set to `PRE_HOOK_ALWAYS_DENY`, the call MUST revert. If any return an `authorizer` value other than 0 or 1, execution MUST revert. If any return an `authorizer` value of 1, indicating an invalid signature, the returned validation data of the outer call MUST also be 1. If any return time-bounded validation by specifying either a `validUntil` or `validBefore` value, the resulting validation data MUST be the intersection of all time bounds provided. Then, the modular account MUST execute the validation function with the user operation and its hash as parameters using the `call` opcode. The returned validation data from the user operation validation function MUST be updated, if necessary, by the return values of any pre user operation validation hooks, then returned by `validateUserOp`. @@ -567,18 +517,20 @@ Additionally, when the modular account natively implements functions in `IPlugin The steps to perform are: -- If the call is not from the `EntryPoint`, then find an associated runtime validation function. If one does not exist, execution MUST revert. The modular account MUST execute all pre runtime validation hooks, then the runtime validation function, with the `call` opcode. All of these functions MUST receive the caller, value, and execution function's calldata as parameters. If any of these functions revert, execution MUST revert. If any are set to `PRE_HOOK_ALWAYS_DENY`, execution MUST revert. If any are set to `RUNTIME_VALIDATION_ALWAYS_ALLOW`, those must not be run and treated as though they did not revert. -- If there are pre execution hooks defined for the execution function, execute those hooks with the caller, value, and execution function's calldata as parameters. If any of these hooks returns data, it MUST be preserved until the call to the post execution hook. The operation MUST be done with the `call` opcode. If any of these functions revert, execution MUST revert. +- If the call is not from the `EntryPoint`, then find an associated runtime validation function. If one does not exist, execution MUST revert. The modular account MUST execute all pre runtime validation hooks, then the runtime validation function, with the `call` opcode. All of these functions MUST receive the caller, value, and execution function's calldata as parameters. If any of these functions revert, execution MUST revert. If any pre runtime validation hooks are set to `PRE_HOOK_ALWAYS_DENY`, execution MUST revert. If the runtime validation function is set to `RUNTIME_VALIDATION_ALWAYS_ALLOW`, the validation function MUST be bypassed. +- If there are pre execution hooks defined for the execution function, execute those hooks with the caller, value, and execution function's calldata as parameters. If any of these hooks returns data, it MUST be preserved until the call to the post execution hook. The operation MUST be done with the `call` opcode. If there are duplicate pre execution hooks (i.e., hooks with identical `FunctionReference`s), run the hook only once. If any of these functions revert, execution MUST revert. - Run the execution function. -- If any associated post execution hooks are defined, run the functions. If a pre execution hook returned data to the account, that data MUST be passed as a parameter to the associated post execution hook. The operation MUST be done with the `call` opcode. If any of these functions revert, execution MUST revert. Notably, for the `uninstallPlugin` native function, the post execution hooks defined for it prior to the uninstall MUST run afterwards. +- If any post execution hooks are defined, run the functions. If a pre execution hook returned data to the account, that data MUST be passed as a parameter to the associated post execution hook. The operation MUST be done with the `call` opcode. If there are duplicate post execution hooks, run them once for each unique associated pre execution hook. For post execution hooks without an associated pre execution hook, run the hook only once. If any of these functions revert, execution MUST revert. + +The set of hooks run for a given execution function MUST be the hooks specified by account state at the start of the execution phase. This is relevant for functions like `installPlugin` and `uninstallPlugin`, which modify the account state, and possibly other execution or native functions as well. #### Calls made from plugins -Plugins MAY interact with other plugins and external contracts through the modular account using the functions defined in the `IPluginExecutor` interface. These functions MAY be called without a defined validation function, but the modular account MUST enforce these checks and behaviors: +Plugins MAY interact with other plugins and external addresses through the modular account using the functions defined in the `IPluginExecutor` interface. These functions MAY be called without a defined validation function, but the modular account MUST enforce these checks and behaviors: The `executeFromPlugin` function MUST allow plugins to call execution functions installed by plugins on the modular account. Hooks matching the function selector provided in `data` MUST be called. If the calling plugin's manifest did not include the provided function selector within `permittedExecutionSelectors` at the time of installation, execution MUST revert. -The `executeFromPluginExternal` function MUST allow plugins to call external contracts as specified by its parameters on behalf of the modular account. If the calling plugin's manifest did not explicitly allow the external contract call within `permittedExternalCalls` at the time of installation, execution MUST revert. +The `executeFromPluginExternal` function MUST allow plugins to call external addresses as specified by its parameters on behalf of the modular account. If the calling plugin's manifest did not explicitly allow the external call within `permittedExternalCalls` at the time of installation, execution MUST revert. ## Rationale @@ -586,7 +538,7 @@ ERC-4337 compatible accounts must implement the `IAccount` interface, which cons The function routing pattern of ERC-2535 is the logical starting point for achieving this extension into multi-functional accounts. It also meets our other primary design rationale of generalizing execution calls across multiple implementing contracts. However, a strict diamond pattern is constrained by its inability to customize validation schemes for specific execution functions in the context of `validateUserOp`, and its requirement of `delegatecall`. -This proposal includes several interfaces that build on ERC-4337 and are inspired by ERC-2535. First, we standardize a set of modular functions that allow smart contract developers greater flexibility in bundling validation, execution, and hook logic. We also propose interfaces that take inspiration from the diamond standard and provide methods for querying execution functions, validation functions, and hooks on a modular account. The rest of the interfaces describe a plugin's methods for exposing its modular functions and desired configuration, and the modular account's methods for installing and removing plugins and allowing execution across plugins and external contracts. +This proposal includes several interfaces that build on ERC-4337 and are inspired by ERC-2535. First, we standardize a set of modular functions that allow smart contract developers greater flexibility in bundling validation, execution, and hook logic. We also propose interfaces that take inspiration from the diamond standard and provide methods for querying execution functions, validation functions, and hooks on a modular account. The rest of the interfaces describe a plugin's methods for exposing its modular functions and desired configuration, and the modular account's methods for installing and removing plugins and allowing execution across plugins and external addresses. ## Backwards Compatibility diff --git a/ERCS/erc-7092.md b/ERCS/erc-7092.md index 0f591f478c..e3e8779bca 100644 --- a/ERCS/erc-7092.md +++ b/ERCS/erc-7092.md @@ -4,7 +4,8 @@ title: Financial Bonds description: Represents debt issued by entities to investors. author: Samuel Gwlanold Edoumou (@Edoumou) discussions-to: https://ethereum-magicians.org/t/financial-bonds/14461 -status: Review +status: Last Call +last-call-deadline: 2024-02-07 type: Standards Track category: ERC created: 2023-05-28 @@ -328,7 +329,7 @@ interface IERC7092CrossChain /** is ERC165 */ { * @param _destinationChainID The unique ID that identifies the destination Chain. * @param _destinationContract The smart contract to interact with in the destination Chain in order to Deposit or Mint tokens that are transferred. */ - function crossChainDecreaseAllowance(address _spender, uint256 _amount, bytes32 _destinationChainID, address _destinationContract) external; + function crossChainDecreaseAllowance(address _spender, uint256 _amount, bytes32 _destinationChainID, address _destinationContract) external returns(bool); /** * @notice Decreases the allowance of multiple spenders in `_spender` by corresponding amounts specified in the array `_amount` on the destination chain @@ -337,7 +338,7 @@ interface IERC7092CrossChain /** is ERC165 */ { * @param _destinationChainID array of unique IDs that identifies the destination Chain. * @param _destinationContract array of smart contracts to interact with in the destination Chain in order to Deposit or Mint tokens that are transferred. */ - function crossChainBatchDecreaseAllowance(address[] calldata _spender, uint256[] calldata _amount, bytes32[] calldata _destinationChainID, address[] calldata _destinationContract) external; + function crossChainBatchDecreaseAllowance(address[] calldata _spender, uint256[] calldata _amount, bytes32[] calldata _destinationChainID, address[] calldata _destinationContract) external returns(bool); /** * @notice Moves `_amount` bond tokens to the address `_to` from the current chain to another chain (e.g., moving tokens from Ethereum to Polygon). diff --git a/assets/erc-6900/Plugin_Execution_Flow.svg b/assets/erc-6900/Plugin_Execution_Flow.svg index b5b013d5e4..3a94b512ed 100644 --- a/assets/erc-6900/Plugin_Execution_Flow.svg +++ b/assets/erc-6900/Plugin_Execution_Flow.svg @@ -1,4 +1,4 @@ - + @@ -11,7 +11,11 @@ font-family: "Cascadia"; src: url("https://excalidraw.com/Cascadia.woff2"); } + @font-face { + font-family: "Assistant"; + src: url("https://excalidraw.com/Assistant-Regular.woff2"); + } - Permitted External Contracts & Methods executeFromPluginPost Permitted Call Hook(s)Pre Execution Hook(s)Pre Permitted Call Hook(s)Permitted Plugin Execution FunctionPost Execution Hook(s)PluginsPlugin Permission Check executeFromPluginExternal(Plugin) Execution Function1 calls plugin 2.2 calls external contracts through executeFromPluginExternalPre Permitted Call Hook(s)Post Permitted Call Hook(s)Plugin Permission CheckModular AccountPlugin Execution Flow2.1 calls other installed plugin through executeFromPluginPre executeFromPluginExternal Hook(s)Post executeFromPluginExternal Hook(s) \ No newline at end of file + Permitted External Contracts & Methods executeFromPluginPre Execution Hook(s)Permitted Plugin Execution FunctionPost Execution Hook(s)PluginsPlugin Permission Check executeFromPluginExternal(Plugin) Execution Function1 calls plugin 2.2 calls external contracts through executeFromPluginExternalPlugin Permission CheckModular AccountPlugin Execution Flow2.1 calls other installed plugin through executeFromPluginPre executeFromPluginExternal Hook(s)Post executeFromPluginExternal Hook(s) \ No newline at end of file