The problem Deva Wallet solves

The world of Web3 products is rapidly expanding, from games to decentralized social networks, and the offerings are increasingly compelling. However, mass adoption is hindered by complex onboarding processes. Many traditional Web2 users distrust and lack knowledge about cryptocurrencies and blockchain protocols. For non-tech people, setting up a Metamask account and processing transactions or buying tokens is too complex. Web3 remains a niche world, accessible only to those familiar with its technical jargon and backend intricacies.

Deva Wallet aims to change that by making Web3 accessible to regular Web2 users. It offers the simplest onboarding experience with just one QR code scan. New users no longer need to obtain a native coin, as transaction fees can be covered by others or paid with traditional methods (Apple Pay/Google Pay).

Dapp owners can sponsor fees for interactions with their smart contracts by deploying a paymaster contract, stacking it into the entrypoint, and registering it into our whitelist contract. Users will see "Tx fees sponsored by <company name>" on the confirmation screen, ensuring a smooth experience for newcomers.

Deva Wallet is compatible with the Wallet Connect standard, allowing it to translate "transactions" to "user operations." This means users can use Deva Wallet with any Dapp on the internet while benefiting from transaction sponsoring and credit card payments.

Additionally, Deva Wallet features transaction outcome simulation. Before confirming a transaction, it performs a dry run and extracts event information from the transaction receipt. This information is presented to the user, showing the assets they will spend or receive if the transaction is executed. This security feature protects users from unintended operations.

In summary, Deva Wallet simplifies the onboarding process, supports traditional payment methods, and offers transaction outcome simulations, making Web3 more accessible and secure for everyone.

Challenges I ran into

• The biggest challenge was the compliance one. It turns out that in order to accept credit card payments for tx fees a company had to introduce a lot of procedures that we didn’t imagine were necessary. We only recently finalized the process of registration into VASP which is required in UE to operate such service legally.
• On the technical front, we struggled a bit to reconcile ERC4337 Account Abstraction with the Wallet Connect protocol. Some creative workarounds were necessary to translate between the two worlds.
• We’re also quite proud of our ability to predict the transaction outcome before it was executed. For this we use a forking feature provided by @nomicfoundation/edr (formerly part of hardhat), to execute a transaction in dry mode and extract receipt logs from it.