For a moment, let’s set aside the talk about bundlers and paymasters and userOps and reverse engineer how we want 🌈Web 3.0🌈 to work.

A hyperpositive vision for post-AA UX would be like:

1. User signs in through their passkey/authentication factor

2. They send transactions in one click

3. When they go to another dApp, and they bring their assets and tx history along with their wallet

4. If the issuing application shuts down, user retains self-custody of the wallet

5. If the user loses the key to the account, they have some way to recover control of it

We want it to have all the EOA’s benefits while having added security and reducing the steps for setup and transaction.

A tall order, but that’s what we aspire for.

Now let’s look at what we currently have with ERC-4337 implemented:

1. User signs in through their passkey/authentication factor

2. They send transactions in one click

3. When they go to another dApp, they get another wallet

4. Has to transfer asset to the other wallet if they want to use it

5. Cannot bridge because the wallet only exists in one chain

6. The wallet is recoverable but there’s no interface for its recovery

There’s still a lot more to be done if we want rich web3 experiences that maximize the power of verifiable ownership and self-custodiality for everyone, which is the whole point of why we’re here.

So what do product designers do?

If you are implementing AA, your target users might not even be aware of these limitations. A straightforward flow works for now. You want to mint them an NFT? Send it straight to a wallet that they can control through their email. Airdropping some tokens to a non-cryptonative community? Do the same thing.

But while tech is being figured out, I’m creating interfaces for smart account recovery, accessibility, and transferability that any application that implements ERC-4337 can use. We’re building for the future. Be first to find it in WAIFU’s website.