-
-
Notifications
You must be signed in to change notification settings - Fork 155
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ZEUS-1419: LNURL-w fixed value patch #1427
Conversation
@kaloudis Is there a CI where can I download binaries for testing? |
@prusnak not yet |
I tried to build via
Not sure what's going on - I have plenty of disk space available. |
@prusnak very interesting. what OS are you running it on? |
macOS 13.1 |
Anyway, here's the QR code with LNURL-w for 10 satoshis to reproduce the issue (amount is set to 0 and editing is disabled): This one contains LNURL-w with range 10-12 satoshis. Amount is still set to 0 by default, but I can edit it and thus withdraw: Maybe the default amount shouldn't be set to zero but set to max? Or better is to set to min so we are not greedy? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
tACK
Description
Relates to issue: ZEUS-1419
Fixed value LNURL-w was not able to be claimed when invoice settings were not defined as it broke the
UNSAFE_componentWillMount
block inviews/Receive
.This pull request is categorized as a:
Checklist
yarn run tsc
and made sure my code compiles correctlyyarn run lint
and made sure my code didn’t contain any problematic patternsyarn run prettier
and made sure my code is formatted correctlyyarn run test
and 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
yarn
after this PR is merged inpackage.json
andyarn.lock
have been properly updatedOther: