QR and Verification feature

[yet300]

Summary

• Add QR-based verification flow with deep link handling and system notifications.
• Add security verification sheet with fingerprints, session state, and verify/unverify actions.
• Persist fingerprint/identity metadata for offline display and sidebar verified badges.

Changes

• VerificationService + mesh handling for verify challenge/response.
• UI: VerificationSheet, SecurityVerificationSheet, verified icons in header/sidebar.
• Identity caching for peer fingerprints and nicknames to support offline views.

Video

FILE.2025-12-31.20.24.30.mp4

Notes

• Deep link handling implemented in app/src/main/java/com/bitchat/android/MainActivity.kt and app/src/main/AndroidManifest.xml.

Checklist

• I have read the contribution guidelines: https://github.com/permissionlesstech/bitchat-android?tab=readme-ov-file#contributing
• I have performed a self-review of my code

• I have mentioned the corresponding issue and the relevant keyword (e.g., "Closes: #xy") in the description (see https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue)
• If it is a core feature, I have added automated tests

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[chatgpt-codex-connector]

Fix unresolved OutlinedWarning icon reference

SecurityVerificationSheet won’t compile: the buildStatusInfo branch for failed sessions references Icons.Outlined.OutlinedWarning, but the only available symbol is the aliased OutlinedWarning/Icons.Outlined.Warning. With the current name, the code does not resolve and the module fails to build, blocking the new verification UI.

Useful? React with 👍 / 👎.

[callebtc]

very nice!

[callebtc]

I have reviewed the implementation and applied the following improvements for robustness and code quality:

Refactoring & Code Quality

• Extracted VerificationHandler: Moved all QR verification logic and state from ChatViewModel into a dedicated VerificationHandler class. This significantly reduces the size of the ViewModel and separates concerns.
• Dependency Injection: The handler is instantiated with necessary dependencies, keeping the architecture clean.

Security & Concurrency

• Thread-Safe Identity Storage: Added synchronized blocks in SecureIdentityStateManager to prevent race conditions during read-modify-write operations on SharedPreferences. This ensures verification state isn't lost if multiple updates happen simultaneously.
• Safe State Management: Switched to ConcurrentHashMap for tracking pending verifications and nonces, ensuring thread safety when handling network callbacks on background threads.

These changes make the feature production-ready and stable.

[callebtc]

Build errors fixed:

• XML Parsing: Escaped all unescaped ampersands in the translated string resources.
• Compilation: Restored missing helper methods and variables in ChatViewModel that were accidentally removed during refactoring.

The app now builds successfully.