Changes to account abstraction clients needed post-EIP-7702

[amiecorso]

EIP-7702 allows EOAs to set code at their address. Viem is already in the process of developing utilities for these account upgrades. This EIP will break some of the assumptions that are baked into how viem currently handles smart contract wallet account clients. Specifically, smart contract wallet addresses are currently deterministically derived using CREATE2, based on the implementation bytecode, and the initcode, which in the case of CoinbaseSmartWallet is an array of owners (either EOA public keys or passkey keys). This deterministically created address is not configurable on the smart wallet client because it is assumed to be inherently linked to the account owners.

Once EIP-7702 is live, any arbitrary EOA will be able to set a code designation at its account and thus behave as a smart contract wallet with some arbitrary set of owners. This breaks the relationship between the owners and the address of the smart contract wallet. Ideally, the smart contract wallet clients in Viem would expose an option to explicitly configure the address of the account, independently of the owners of the account. What do you think?

[jxom]

This is already possible. You just need to explicitly pass an address to toCoinbaseSmartAccount.

[amiecorso]

ah, thank you! I'll close this discussion.