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
Overview of erc4337
Erc4337 allows account abstraction without changing consensus protocol on ethereum. Since smart contract can’t initiate a transaction, erc4337 introduces Bundlers to collect UserOperations and wrap them as normal ethereum transactions. The transactions sent by a Bundler will be executed by a EntryPoint smart contract and bill the sender’s smart contract wallet. Docs can be found here.
Ways for support erc4337 on Meson
Use third-party bundler node provider that provides erc4337 function:
Doesn’t need to update meson provider's workflow, only updates supported command in plugin.
Adds support for erc4337 transaction in meson-plugin
In command/ethereum.go, add new command for (eth_sendUserOperation, eth_estimateUserOperationGas)
In ethereum_chain.go add new ethRequest method for eth_sendUserOperation and eth_estimateUserOperationGas
(The detail of erc4337 RPC methods can be found here)
The node provider used in Meson needs to support erc4337 (e.g. Stackup/Alchemy)
Implement bundler on meson mixnet provider:
Updates meson-plugin to accept erc4337 tx
Requires access to a full-node with debug API enabled for tracing (for simulating transactions to validate userOp)
Basic workflow for meson provider bundler:
Receives UserOperation
Validates UserOperation
(Full validation process can be found here)
Add UserOperation to a private Mempool
Collect a batch of UserOperation and create a eth transaction to call entrypoint.handleOps(ops: [UserOperations], beneficiary: provider’s address)
(Sender of the transaction will be meson provider’s account, and thus we need to maintain a funded account on chain.)
Overview of erc4337
Erc4337 allows account abstraction without changing consensus protocol on ethereum. Since smart contract can’t initiate a transaction, erc4337 introduces Bundlers to collect UserOperations and wrap them as normal ethereum transactions. The transactions sent by a Bundler will be executed by a EntryPoint smart contract and bill the sender’s smart contract wallet. Docs can be found here.
Ways for support erc4337 on Meson
Use third-party bundler node provider that provides erc4337 function:
Doesn’t need to update meson provider's workflow, only updates supported command in plugin.
Adds support for erc4337 transaction in meson-plugin
(The detail of erc4337 RPC methods can be found here)
The node provider used in Meson needs to support erc4337 (e.g. Stackup/Alchemy)
Implement bundler on meson mixnet provider:
Updates meson-plugin to accept erc4337 tx
Requires access to a full-node with debug API enabled for tracing (for simulating transactions to validate userOp)
Basic workflow for meson provider bundler:
(Full validation process can be found here)
(Sender of the transaction will be meson provider’s account, and thus we need to maintain a funded account on chain.)
Resources
https://eips.ethereum.org/EIPS/eip-4337
https://docs.stackup.sh/docs/introduction/account-abstraction
https://www.alchemy.com/blog/account-abstraction
Stackup’s Bundler implementation
Infinitism's 4337 Implementation (core EIP-4337 team)
The text was updated successfully, but these errors were encountered: