[Core Protocol] EIP-6492

[kouraf]

Issue Description

Hello, I want to use account abstraction and EIP-6492 when the wallet still doesn't exist but it seems to not work in OP.
can you tell me why? basically, EIP-6492 is a way to create a contract and simulate a call on it for free using an eth_call so you do not allow it? do you have an alternative?
you can see in my example that it works with Arb and i tried it in many other evms and it works too.
example here

Additional Information

No response

[sbvegan]

Hey @kouraf, I'm not sure about this one. Let me see if I can find someone who knows when/if this will be supported.

[sbvegan]

Here's what I found out from a client engineer:

That is completely at the app layer and we are 1:1 with Ethereum so there is likely a bug in their code. Perhaps they could try to get it working on L1 first to show it then it should just work on L2

[kouraf]

Hello @sbvegan thanks for the response, I already provided in the issue an example where it works in Arbitrum but doesn't work in Optimism and here is a new one with Ethereum here

I am happy to help with further details if needed.

[sbvegan]

The evm op codes are not showing any PUSH0 instructions

[smartcontracts]

@kouraf your code seems to rely on the existence of this factory contract: https://arbiscan.io/address/0x33ddf684dcc6937ffe59d8405aa80c41fb518c5c. This contract did not exist on OP Mainnet. I went ahead and created the contract but it seems that the contract needs to be initialized by an owner. I do not have access to this owner and I'm not sure what this contract is meant to do.

[sbvegan]

Thanks @smartcontracts

Some additional information that I got from another engineer:

They rely on the deterministic deployment address to be set as an allowed implementation in the MultiECDSAFactoryPatch contract, but it's only set to true on a few networks (not including OP mainnet).
see contract #3 in the source @ https://basescan.org/address/0x33DDF684dcc6937FfE59D8405aA80c41fB518C5c#code

[clabby]

This looks to be a configuration issue with your MultiECDSAFactoryPatch contract (0x33DDF684dcc6937FfE59D8405aA80c41fB518C5c).

This creation code relies on the deterministic deployment address of the created account to be set as an allowed implementation in the MultiECDSAFactoryPatch contract, but it's only set to true on a few networks (not including OP mainnet).

It can be seen that we fail here because the implementation is not allowed (sim on OP mainnet)

And this lines up with the isAllowedImplementation calls across the networks as well.

Network	Works?	isAllowedImplementation(address) res for deterministic deployment
ETH Mainnet	✅	true
OP Mainnet	❌	false
OP Goerli	❌	false
OP Sepolia	❌	false
Base Mainnet	✅	true
Base Goerli	✅	true
Base Sepolia	❌	false

See contract #3 (KernelFactory.sol)'s createAccount function in the verified source @ https://basescan.org/address/0x33DDF684dcc6937FfE59D8405aA80c41fB518C5c#code

[github-actions[bot]]

Hey @kouraf, We hope your recent question was resolved to your satisfaction. Your feedback is invaluable and helps us improve our support services. Could you spare a moment to fill out a short feedback survey. Thank you for helping us improve our developer community.