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

1/ I've open-sourced my solution for using a beacon proxy with ERC4337 smart contracts, a problem many devs face.

https://github.com/pavlovdog/4337-beacon-proxy

Thanks to @johnrising and @hazim from @stackup and @konrad for their help and comments on it.

↓🧶

22 • abstractooor @rhinestone • prev oxford and exited web2 founder

Co-founder of stackup.sh (YC S22) & creator of the ERC-4337 Go Bundler.

2/ Beacon proxies may be helpful in many cases, and using them in AA immediately intrigued me (leaving aside the question of the risks of such a solution). Due to the restrictions of the EIP4337 protocol, using a naive solution (eg, OZ implementation) won't work because it violates some rules of the EIP.

Full-time builder. Pimlico | @33bits | farcaster-solidity. Zero-knowledge and asynchronous transactions evangelist.

3/ My implementation solves all the problems with ERC4337 compatibility by providing a custom BeaconProxy contract. By using it and a custom factory (reference implementation included), anyone can build their beacon proxy accounts on top of it. More details are provided in the repo’s README.

4/ As an example, here’s the AA transaction on @base Sepolia, sent with @stackup bundler.

https://sepolia.basescan.org/tx/0x29a511629b7ae9f1c3727621234acfe784e3da6bf357ba1b7377f3e62d23abd0

The stack trace says for itself 😄