[DRAFT] EOA Upgrade

[devbugging]

WIP

[devbugging]

@bluesign Does this design seem safe to you?

[bluesign]

I think 7702 here is the best way for compatibility.

I don't believe we need multiple coa using single eoa. ( but below logic also allows that )

I am not too familiar with evm world, but from what I learned from @mpeter this should be possible.

My imagination was:

• eoa sets coa as code pointer with 7702
• coa has a code that forwards calls ( pretty much the code you shared , but I think revert reason should be from call directly )
• when forward call called it checks if msg.sender is code pointer at current address.

Only issue here is eoa will have code, but I think 7702 mentions that already.

Wallet flow should be something like:

• create eoa
• create coa
• set code of eoa to coa via 7702
• set eoa address on coa (below)

Coa knowing about eoa part can be handled after 7702, calling something on coa to set eoa address.

Using full 7702 builds more trust that we dont have ability to take over any eoa.