-
Notifications
You must be signed in to change notification settings - Fork 2
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
Handle LNURL's #38
Handle LNURL's #38
Conversation
30b3138
to
4c59833
Compare
03be4ac
to
7a84aa4
Compare
7a84aa4
to
4d6bbaf
Compare
dcf0a9f
to
58bc665
Compare
4d6bbaf
to
9d94453
Compare
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.
I think it looks good.
Perhaps we need to use the newly added fetchLightningLimits()
function to check the selected pay/withdraw amounts are within the send/receive swap limits. Or maybe combine the min/max sendable/withdrawable with the swap limits to get unified limits
e1d4c0b
to
f25afa2
Compare
Applied this on LnUrl payments, limits on withdraw flow will be applied on new UI due to an incompatibility. |
f25afa2
to
a67a108
Compare
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.
LGTM
* Validate LnUrl payments against lightning limits * Rename isLnurlPayment to isLnUrlPayment for consistency of capitalization of LnUrl
a67a108
to
266470e
Compare
This PR addresses
#30
LNURL-Pay, LNURL-Withdraw, LNURL-Auth are now handled on l-breez app.
Other changelist:
parseInput
API is no longer a sync function