The problem Safe Surf solves

Issues surrounding the safeguarding of private keys or seed phrases pose considerable risks to users, potentially resulting in irreversible loss of funds. Furthermore, reliance on custodial solutions for prolonged periods lacks sustainability.

Recovery mechanisms are often overly simplistic in conventional systems, contrasting sharply with the complexity of current wallet ecosystems, where the retrieval of lost keys and passwords presents significant challenges.

Transaction transparency is compromised, with users frequently unable to comprehend the intricacies of transaction requests within existing wallets. Consequently, they are compelled to place blind faith in the developers of smart contracts.

The prevalence of scams, including phishing schemes, rug pulls, and flawed smart contracts, has led to substantial financial losses amounting to billions in cryptocurrencies.

Despite the vast potential of blockchain technology, wallets remain restricted primarily to decentralized finance (DeFi) functionalities, limiting their utility.

Interoperability concerns persist, as the majority of wallets offer support for only a select few blockchain networks. This necessitates users to create multiple wallets to engage with diverse blockchain ecosystems.

Challenges we ran into

1. Compatibility Issues: During development, integrating biometric protection and other security features posed challenges due to compatibility issues with existing systems and platforms. Ensuring seamless integration across different devices and operating systems required extensive testing and modifications.

2. Cost Constraints: Integrating advanced security features such as biometric protection incurred significant costs, making it difficult to include them within the project's budget constraints. Balancing security requirements with financial limitations necessitated careful consideration and prioritization of features.

3. Technical Complexity: Implementing OAuth, HMAC, and MPC for enhanced security and recovery options introduced technical complexities during development. Ensuring the robustness and reliability of these mechanisms required thorough understanding and expertise in cryptographic protocols and algorithms.

4. Resource Limitations: Developing a mobile-first wallet using Flutter faced resource limitations, especially regarding available libraries and developer support. Overcoming these limitations required extensive research, exploration of alternative solutions, and potentially developing custom libraries and functions.

5. Competitive Landscape: Building a wallet in a market dominated by TypeScript/Javascript-based solutions presented challenges in terms of differentiation and adoption. Overcoming this hurdle involved devising strategies to showcase the unique advantages and features of the Flutter-based wallet while addressing any potential concerns or barriers to entry.