Ethereum Account Abstraction

It’s weirdly satisfying debugging erc4337 issues. The process really tests your understanding of the EVM and I’ve learnt so much about it in the process

cypherpunk wannabe, engineer working on @frames /open-frames /opencast
https://stephancill.co.za create stories at https://stories.steer.fun

app.intersend.io | sequence. pimlico. poap. polygon. consensys. paxful. flipside crypto. dash. bridgewater. darpa. secdef. navy. dia | linktr.ee/alexanderchopan

The specific thing I’ve been working on over the past couple of evenings is setting up my own bundler to test userop transactions in open browser wallet locally on a mainnet fork using @alchemyplatform’s Rundler implementation (which is awesome btw). Not quite working yet but making progress. Being able to test locally on a mainnet fork will speed up development iterations a lot

Getting to this point required some minor tweaks in viem to get the new experimental bundler client to communicate with it properly as well as building a new connector for wagmi that can use it. Will hopefully open some PRs in the coming days

Base

troubleshooting coinbase paymaster/bundler issues just got A LOT easier

✅  filterable, real-time error logs right in dashboard

✅  detailed view of date, method, error code/message, request

✅  userops export (no longer commingled with error logs)

✅  troubleshooting docs debugging common issues 
https://docs.cdp.coinbase.com/paymaster/docs/paymaster-bundler-troubleshooting

https://x.com/abcrane123/status/1839390280203817198

trying to make this a lot easier. would love feedback on this recent launch!

trying to make this a lot easier. would love feedback on this recent launch!

https://warpcast.com/nickprince.eth/0x5ea423bf

I definitely found this to be true! 

When first working with 4337 last summer, i remember diving deep with foundry to find the source of issues because the call trace goes super deep but the bundler providers would only surface the error code 😅

We definitely need to make this easier

You need to embrace it 🧘

(viem has made it a lot nicer)

debugging 4337 is an actual pain in the ass 🤣

It’s a bit harder when you can’t change contract source

Simulation/tracing tools like tenderly are very helpful

I also end up making extensive use of patching to console.log intermediate values in viem 😅

The foundry suite is also nice (anvil/cast)

How you debug? I use this console log from hardhat is there a better way?

There should be a channel called Dev-challenges😅
Contents like this, could go there 

It’s always fulfilling to solve a problem and deriving satisfaction

Is there anything you learnt that you considered gatekeeping but on a second thought would like to share?