Content pfp
Content
@
https://opensea.io/collection/evm-6
0 reply
0 recast
2 reactions

Paul Berg pfp
Paul Berg
@prberg
If I could wave a magic wand and make one addition to the EVM spec of 2015, that'd be a feature to allow EOAs to specify multiple contract entry points in txs. It's hard to overstate how many features are impossible to implement in an EVM app due to this missing functionality.
3 replies
0 recast
7 reactions

Paul Berg pfp
Paul Berg
@prberg
Cc @vitalik.eth Will this functionality ever implemented in the EVM? Or is it that account abstraction will effectively solve this?
2 replies
0 recast
1 reaction

Skeletor Spaceman  pfp
Skeletor Spaceman
@skeletor
hopefully yes! either native or contract account abstraction would work for this. native AA would allow contracts to execute code as-if they were the tx.origin EOA. good thing is that this is already possible for contract AA, but since everything is design to interact with EOAs, not that much changes. i.e. approve+call
0 reply
0 recast
1 reaction