Integrating EIP-4337 into your Universal Profile
This guide assumes that you are already familiar with the EIP-4337 standard and Universal Profiles.
Prerequisites for Integrationâ
Key Managerâ
The Universal Profile contract must be owned by a KeyManager contract.
Bundlersâ
Bundlers are the key component of the EIP-4337 protocol. They are responsible for bundling UserOperations into transactions and submitting them to the EVM blockchain. You will need to run your own bundler or use a third-party service on your behalf. See the Ethereum implementation of their bundler.
Deposit on the EntryPoint contractâ
The EntryPoint contract is the entry point for the EIP-4337 protocol. It is responsible for receiving UserOperations and forwarding them to the appropriate account. In order to use the EntryPoint contract, you must first deposit a certain amount of native token on the contract. This deposit is used to pay the bundlers for their services.
Have a controller with the 4337 Extension Permissionâ
The controller of the Universal Profile that will use the 4337 extension must have the _4337_PERMISSION permission in order to use it. To learn more about permissions, refer to the LSP6 standard.
Deployment of the 4337 Extensionâ
In order to integrate the 4337 extension, you must first deploy the Extension4337.sol or have the address of an already deployed instance of the 4337 extension contract.
Extend your Universal Profile with the 4337 Extensionâ
Once you have deployed the 4337 extension, you can extend your Universal Profile with the 4337 extension by adding support to the validateUserOp (selector 0xfff35b72) function in your Universal Profile contract. You can follow the following tutorial to add an extension to your Universal Profile.
Using the 4337 Extensionâ
Once you have extended your Universal Profile with the 4337 extension and followed all the prerequisites above, bundlers can call the handleOps function of the EntryPoint contract to execute UserOperations on your Universal Profile.