-
Notifications
You must be signed in to change notification settings - Fork 913
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
paying to invoice with deschashonly=true not working #6085
Comments
i'm aware that it works with simple descriptions like "test". But this one does not. I tried to .encode() the description but then i get |
example python script:
|
They broke description_hash in 23. Soooo, yeah. |
tried the same thing with cln-plugin using |
also, on the cli i could pay the invoice with |
Looks like non-issue for v23.05. I think issue may be closed @rustyrussell @cdecker. |
it might be an issue again if description is required even with allow-deprecated-apis=true (maybe in 23.08?). If this happens i would not know how pyln-client and cln-rpc would |
I agree that this should be closed, as mentioned by @evd0kim. The issue discussed here [1] is not a problem on the cln side. Additionally, the specification side is addressed in [2]. The only possible solution is to fix the protocol to use only hash description. Unfortunately, the proposal to drop the requirements did not receive enough support, as it received 3 NACKs. Therefore, it seems unlikely that this change will happen. [1]: GitHub Issue: ElementsProject/lightning#6092 |
I'm so confused. Are plugins with pyln-client or cln-rpc supposed to be able to pay invoices with description_hash and description or not? Because if yes then this issue is about certain descriptions not working with pyln-client/cln-rpc while they do work directly on the cli. |
Oh, sorry. I thought the problem is that i couldn't generate such invoices. May be it shouldn't be closed indeed. |
Mh sorry I was answering the following message
Mh so there are more than a couple of things here, let's recap a little bit to answer your questions:
You may be passing the wrong parameters to the pay argument, what are your commands to pass to lightning-cli |
|
if you reread my 1. and 3. post you can see it doesn't work and i dare you to proof me wrong :) |
Yeah, this looks strange, I will look into it |
very simple python script basically 2 lines:
cln = LightningRpc("/home/bitcoin/.lightning/bitcoin/lightning-rpc")
and then the call to pay and later invoice:
sha256sum seems fine:
echo -n '[["text/plain","Funding @odell on stacker.news"],["text/identifier","odell@stacker.news"]]' | sha256sum da1ed03d172c9bba7cb7a06b1580f660451b1687b8d87d07607a99b72b84c154 -
double check the other way around:
I don't get it. hash seems fine.
The text was updated successfully, but these errors were encountered: