The problem Xeba solves

Scams: Scams like phishing attacks and faulty smart contracts have resulted in billions of dollars of lost cryptocurrencies.

Limited Functionality: Existing wallets often provide limited DeFi functionalities despite the potential of blockchain technology.

Interoperability: Most wallets support only a few blockchains, necessitating multiple wallets for interacting with different networks.
Secure Storage: Users risk losing funds when storing private keys or seed phrases, and relying on custodial solutions involves trusting third parties.

Limited Recoverability: Current wallet ecosystems lack sufficient recovery options for lost keys and passwords.

Transaction Readability: Users struggle to understand transaction requests, leading to blind trust in smart contract developers and potential risks.

Challenges we ran into

IS THE SOLUTION SAFE ENOUGH AND DOES IT HAVE ENOUGH RECOVERY OPTIONS?
Our solution is more secure than 90% of the existing wallets. We thought of improving it further with biometric protection, but ran into problems as integrating those solutions were too costly, hence we couldn't include them. So, we just added OAuth, HMAC, and MPC for now to make it more secure while also enabling easier recovery options than existing solutions.

What might be the problems faced during development?
We are planning on building a mobile-first wallet using Flutter, but as soon as we started exploring, we noticed that 95% of existing wallets are built using either TypeScript/Javascript. Hence, due to this, the Flutter libraries are distributed and aren't developer-friendly. We are trying to overcome this issue with our extensive research and by creating our own core functions and libraries by exploring options available in other coding languages.