Conversation
Summary of ChangesHello, I'm Gemini Code Assist1! 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 significantly upgrades the Cashu payment system by enabling multi-mint sends. This feature allows users to aggregate funds from several Cashu mints to complete a single payment, improving the user experience by providing more robust payment options. The changes span across the core Cashu DevKit, the application's data stores, and various user interface components to seamlessly integrate this new capability. Highlights
Changelog
Activity
Using Gemini Code AssistThe 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
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 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
|
There was a problem hiding this comment.
Code Review
This pull request introduces a significant new feature: multi-mint sends for Cashu ecash. This allows users to pay Lightning invoices using funds from multiple mints simultaneously. The changes are extensive, touching native Android and iOS code, the TypeScript bridge, data stores, and multiple UI components.
My review focuses on the new logic and its integration. I've identified opportunities to reduce code duplication in the native modules for both Android and iOS, which will improve maintainability. The overall implementation of the multi-mint payment flow, including the UI for mint selection and the payment progress screen, appears robust and well-designed.
f6a6870 to
4445487
Compare
8a9cbb3 to
611117d
Compare
|
@a-khushal, Please resolve branch conflicts |
8b7d1cb to
1f4de93
Compare
|
Current UI selection clashes with Random mint selection for receives, we have to reconcile that. |
1f4de93 to
101ea1b
Compare
b458178 to
86cfeab
Compare
…lances after payment
…t view, and show invoice details on insufficient funds
… details to payment sheet
…alance sync to background
… mint to single mint fix lnurl ecash flow to continue on not enough funds error
66d7462 to
36eec46
Compare


Description
Relates to issue: ZEUS-2951
Most of the code's been taken from #3177
This pull request is categorized as a:
Checklist
yarn run tscand made sure my code compiles correctlyyarn run lintand made sure my code didn’t contain any problematic patternsyarn run prettierand made sure my code is formatted correctlyyarn run testand made sure all of the tests passTesting
If you modified or added a utility file, did you add new unit tests?
I have tested this PR on the following platforms (please specify OS version and phone model/VM):
I have tested this PR with the following types of nodes (please specify node version and API version where appropriate):
Locales
Third Party Dependencies and Packages
yarnafter this PR is merged inpackage.jsonandyarn.lockhave been properly updatedOther: