ERC4337 enabling AA for Ethereum

Thanks for sharing the work @K9QfAg6 — the repo/resource itself is useful.

AOB works best when posts are framed as discussion-first, not only announcements or link drops.
Please add a follow-up comment covering:

• target audience,

• biggest challenge,

• common confusion point,

• and a specific question for members.

Once that’s added, this becomes much more valuable for both community discussion and future readers.

Thanks for the nudge @ShubhadaJP , adding a bit more context here.

My Target audience:
Mostly Solidity devs who want to really understand ERC-4337 from the inside out. Not just “use a library and it works,” but actually see how UserOperations move through the system, how EntryPoint orchestrates things, and how validation and execution are separated.

What was hardest while putting this together:
Getting a clean mental model of validation vs execution. Once I properly understood how validateUserOp, deposits, bundler simulation, and gas guarantees all fit together, the whole design made sense. Before that, it honestly felt fragmented.

Some confusion points I tried to address clearly:

• Where the nonce actually lives (EntryPoint, not inside the wallet)

• What exactly is being signed (userOpHash, not arbitrary calldata)

• How gas is guaranteed before execution happens

• Why bundlers simulate off-chain

• How this works without changing Ethereum’s core protocol
  - and every query that pops up in our minds going through this!

Curious to hear from others building with 4337:
If you’ve implemented it in a real project, what caused you the most friction? Nonce race conditions? Paymaster edge cases? Simulation mismatches? Bundle-wide reverts?

Would love to hear practical lessons from people who’ve gone beyond tutorials.