A place for talking about the Ethereum Virtual Machine on Farcaster.

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.

Co-Founder at sablier.com, and open-source developer. I have a broad range of interests, including longevity, epistemology, physics, and psychology.

Cc @vitalik.eth

Will this functionality ever implemented in the EVM?

Or is it that account abstraction will effectively solve this?

What do you mean by multiple contract entry points? Like, make multiple calls?

If so, yes, AA makes that trivial.

Yes, multiple calls, but specifically, calling multiple functions in different contracts.

See PRBProxy  - I've spent weeks building this, but I wish I didn't have to (because the VM provided this instead).

PRBProxy is like Maker's DSProxy if you happen to be familiar with it.

Yes, multiple calls, but specifically, calling multiple functions in different contracts.

See PRBProxy  - I've spent weeks building this, but I wish I didn't have to (because the VM provided this instead).

PRBProxy is like Maker's DSProxy if you happen to be familiar with it.

https://github.com/PaulRBerg/prb-proxy

Happy new year Vitalik.

What do you think it's the biggest obstacle yet for AA adoption?

There are a few non-custodial solutions live, but still haven't seen much applications offering it.