Email verification

[niteshbalusu11]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @niteshbalusu11, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request implements a comprehensive email verification system, integrating it into the user registration and onboarding flow. The goal is to ensure users verify their email addresses, which is essential for account security and unlocking all wallet features like payments and backups. The solution spans both client-side (React Native) for user interaction and server-side (Rust) for handling email sending via AWS SES, code storage in Redis, and database updates to track verification status.

Highlights

• Email Verification Flow: Introduced a new email verification step during user registration and onboarding to enhance account security and enable full wallet functionality. This includes client-side UI for email and code input, and server-side logic for sending and validating verification codes.
• AWS SES Integration: Integrated with AWS Simple Email Service (SES) on the server to reliably send verification emails to users. A development mode is included to log emails instead of sending them in non-production environments.
• Redis for Code Storage: Implemented a Redis-based store for temporary email verification codes, ensuring codes have a 10-minute time-to-live (TTL) for security and to allow for resending.
• Database Schema Update: Modified the users table in the database to include email and is_email_verified fields, along with a partial unique index on the email column.
• Client-Side UI Components: Added a new EmailVerificationScreen for users to enter their email and verification code, and an EmailVerificationBanner to prompt unverified users on the home screen.
• Onboarding Flow Adjustment: Updated the client's onboarding navigation to direct users to the new EmailVerificationScreen after mnemonic setup, ensuring email verification is a mandatory step before proceeding to Lightning Address setup.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request introduces a comprehensive email verification flow, touching both the client and server codebases. The changes are well-structured, including new API endpoints, database migrations, client-side screens, and thorough testing. The new onboarding flow is logical, and the code is generally clean and maintainable.

I've identified a critical compilation issue in the Rust code for random code generation and a couple of medium-severity suggestions on the client-side to improve code quality and prevent potential bugs. Once these are addressed, this will be a solid contribution.

[niteshbalusu11]

/gemini review

[gemini-code-assist]

Code Review

This pull request introduces a comprehensive email verification feature, touching both the client and server. The changes include new UI screens, updates to the onboarding flow, new API endpoints, database schema changes, and services for sending emails and managing verification codes. The implementation is robust, with good test coverage for the new server-side logic. However, I've identified a few critical issues that need to be addressed before merging. A key security middleware for checking email verification is currently disabled, and there's a compilation error in the server's code generation logic due to outdated library usage. Additionally, there's a minor issue with React hook dependencies on the client side that should be corrected for better stability.