-
Notifications
You must be signed in to change notification settings - Fork 139
Issues: lnurl/luds
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
LUD-01: Recommendation to add CORS headers for all server responses
#259
opened May 12, 2024 by
adambor
LUD-03: Provide recommendation for zero balance withdrawal response
#232
opened Aug 21, 2023 by
wbobeirne
LUD-04 Spec Addition: k1 value should be optional and trigger a negotiation step like LUD-06.
#229
opened Aug 9, 2023 by
cmdruid
Misleading "supported" table for LUD-01 in README (fallback support)
#208
opened Mar 31, 2023 by
vindard
Proposal for LUD-03 spec addition: wallet must nod send an invoice with tag
h
in callback
#206
opened Mar 14, 2023 by
johnzweng
LUD-03: withdrawRequest k1 should be signed using same key derived from LUD-04
#169
opened Jun 15, 2022 by
cmdruid
Mobile Wallets: Open LNURLs via a custom scheme such as a wallet name, e.g ZEBEDEE:
#143
opened Feb 10, 2022 by
jackeveritt
Adding encrypted/decrypted pin (used in LNURLPoS/LNURLVend) workflow to protocol?
#136
opened Dec 14, 2021 by
arcbtc
<domain> is very limited in LUD-16, add additional DNS record types to allow flexibility
#93
opened Sep 12, 2021 by
AndySchroder
Previous Next
ProTip!
Add no:assignee to see everything that’s not assigned.