The problem Zephyr Wallet solves

Account abstraction has for a long time been a dream of the Ethereum developer community. Instead of EVM code just being used to implement the logic of applications, it would also be used to implement the verification logic (nonces, signatures…) of individual users’ wallets. Below are some of the features that can be possible using account abstraction:

• Multisigs and social recovery
• More efficient and simpler signature algorithms (eg. Schnorr, BLS)
• Post-quantum safe signature algorithms (eg. Lamport, Winternitz)
• Upgradeability

It is possible to do all of these things with smart contract wallets today, but the fact that the Ethereum protocol itself requires everything to be packaged in a transaction originating from an ECDSA-secured externally-owned account (EOA) makes this very difficult. Every user operation needs to be wrapped by a transaction from an EOA, adding 21000 gas of overhead. The user needs to either have ETH in a separate EOA to pay for gas, and manage balances in two accounts, or rely on a relay system, which are typically centralized.

All of these problems prevent / deter users from exploring the Web3 space.

Challenges we ran into

• Poor, inconsistent, laggy, and patchy internet connection throughout the event at the venue was a big deterrent
• Lack of doumentation on EIP4337 as it is brand a new proposal and still under research
• Creation of the complex EntryPoint, Factory and ERC4337 smart contracts
• Architecting the complex interactions between the smart contracts, the frontend, the bundler and the subgraph
• Problems with the testnets as they were too congested and weren't stable