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
Describe the bug Add option to specify label/description when sending a payment to a keysend address.
c-lightning REST api "/pay/keysend" has a "label" parameter for specifying label/description.
Be nice to scroll through payment history and have descriptions for what I paid for!
To Reproduce Steps to reproduce the behavior: N/A
Expected behavior N/A
Screenshots N/A
Desktop (please complete the following information): N/A
Smartphone (please complete the following information):
Additional context Using c-lightning REST interface
The text was updated successfully, but these errors were encountered:
We now have an internal notes feature you can use for this
Sorry, something went wrong.
After #2723 is merged, it is all done for LND.
CLN is todo though (I didn't look into CLNs capabilities of keysend and keysend message).
OP is talking internal memos. This is already supported. Closing.
Feel free to reopen if you don't think the current functionality addresses your use case.
No branches or pull requests
Describe the bug
Add option to specify label/description when sending a payment to a keysend address.
c-lightning REST api "/pay/keysend" has a "label" parameter for specifying label/description.
Be nice to scroll through payment history and have descriptions for what I paid for!
To Reproduce
Steps to reproduce the behavior:
N/A
Expected behavior
N/A
Screenshots
N/A
Desktop (please complete the following information):
N/A
Smartphone (please complete the following information):
Additional context
Using c-lightning REST interface
The text was updated successfully, but these errors were encountered: