add lnurl_auth and lnurl_withdraw to sndev#2662
Open
pory-gone wants to merge 2 commits intostackernews:masterfrom
Open
add lnurl_auth and lnurl_withdraw to sndev#2662pory-gone wants to merge 2 commits intostackernews:masterfrom
pory-gone wants to merge 2 commits intostackernews:masterfrom
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This fix closes #919 #920
Added lnurl_auth and lnurl_withdraw commands to the sndev CLI tool for local testing. Both commands decode LNURL bech32 strings, interact with the Lightning Network node, and send authenticated responses to callback URLs. I used inline Node.js execution within the app container with existing dependencies.
Screenshots
Additional Context
The lnurl_auth command was tested end-to-end with createAuth mutation and successfully authenticated. The lnurl_withdraw command was tested for LNURL decoding and invoice generation logic but requires an external LNURL-withdraw service (like LNbits) for complete end-to-end testing.
Checklist
Are your changes backward compatible? Please answer below:
Yes
On a scale of 1-10 how well and how have you QA'd this change and any features it might affect? Please answer below:
7/10
For frontend changes: Tested on mobile, light and dark mode? Please answer below:
NaN
Did you introduce any new environment variables? If so, call them out explicitly here:
NaN
Did you use AI for this? If so, how much did it assist you?
AI assisted me in the exploration of LNURL protocol details and cryptographic operations.