We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
For LNbits Node Backend Type accept an LNbits LNURLp in the Host field and instead of synthesising the LNURLp parameters directly obtain them from:
LNURL1DP68GURN8GHJ7MRWVF5HGUEWVDHK6TMVDE6HYMRS9ASHQ6F0WCCJ7MRWW4EXCTEHXQUQWSA9LF
aka
https://lnbits.com/lnurlp/api/v1/lnurl/708
Returning
{ "callback": "https://lnbits.com/lnurlp/api/v1/lnurl/cb/708", "maxSendable": 1337, "metadata": "[[\"text/plain\", \"Lightning Address LNURLp\"]]", "minSendable": 1337, "tag": "payRequest" }
This gives Lightning Address capability with LNbits configuration, handling and response allowing fixed or different range payments and webhooks.
The text was updated successfully, but these errors were encountered:
Good idea.
Sorry, something went wrong.
No branches or pull requests
For LNbits Node Backend Type accept an LNbits LNURLp in the Host field and instead of synthesising the LNURLp parameters directly obtain them from:
LNURL1DP68GURN8GHJ7MRWVF5HGUEWVDHK6TMVDE6HYMRS9ASHQ6F0WCCJ7MRWW4EXCTEHXQUQWSA9LF
aka
https://lnbits.com/lnurlp/api/v1/lnurl/708
Returning
This gives Lightning Address capability with LNbits configuration, handling and response allowing fixed or different range payments and webhooks.
The text was updated successfully, but these errors were encountered: