MiiWallet

Demo

About

The problem it solves Currently, the vast majority of wallets available to regular users are externally owned accounts (EOAs). And while EOAs provide the basic functionalities for sending, receiving, and storing funds, they all function in the same way. This means that EOAs are not only all vulnerable to the same attacks, but they can't provide a personalized user experience beyond their UI. Our custom wallet generator uses the EIP 4337 standard to create smart contract wallets for users, based on their personal needs and specifications. While we didn't have time to implement all of the features we envisioned for this project, we began by implementing multi-signature strucure to allow users to specify existing accounts that must approve transactions for the wallet before they are executed. Other ideas we had included a customized monthly spending limit, mulitfactor authentication across a user's devices, and session tokens that can sign many transactions within a time period without prompting the user. In a final form, our application would allow users to select which elements they want to implement in their wallets and create a smart wallet that fits their specific needs. Our vision for this application is to contribute to better and more intuitive user experiences with wallet creation and use, as well as good security practices which are familiar and user-friendly.

How it's made

Challenges we ran into The greatest challenge we faced in implementing this application was deployment. It was difficult to deploy our contracts locally because the EIP 4337 standard uses an alternative mempool and needs an entrypoint contract deployed on the network. We spent a lot of time writing and configuring scripts in attempt to deploy on the Goerli testnet before eventually being successful in deploying on the Arbitrum testnet. Due to the time we spent initially trying to deploy, we didn't have time to implement many of the features that would have created a custom user experience that we envisioned. However, we were able to deploy our multi-signature contract which conforms to the EIP 4337 standard, which we believe serves as a powerful groudwork and proof of concept for our idea. As it stands now, a user can enter addresses of signers for their wallet transactions, as well as the number of signers required to approve a transaction in order for it to execute.