Skip to content
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

Keysend feature bit announcement #5044

Closed
Ale1ster opened this issue Feb 18, 2021 · 5 comments · Fixed by #6414
Closed

Keysend feature bit announcement #5044

Ale1ster opened this issue Feb 18, 2021 · 5 comments · Fixed by #6414
Assignees
Milestone

Comments

@Ale1ster
Copy link

Background

c-lightning and eclair have implemented keysend, assigning the feature bit 54/55 for it.

Since it is finally adopted and implemented by the other daemons under the above feature bit pair, I think it would be better, for compatibility reasons at least, to announce it as a node feature as well.

Currently, when sending keysend payments from c-lightning v0.9.3 to lnd v0.11.1-beta, it fails due to the missing feature bit.
That is due to a strict requirement for the feature bit from c-lightning, but since it became adopted, wouldn't it be better if the corresponding feature was announced by the lnd nodes for compatibility?

As far as I have seen, the keysend feature bit has not been implemented yet, at least up until lnd v0.12.0-beta.

Keysend feature assignment proposal
c-lightning keysend to lnd error

c-lightning keysend MR
eclair keysend MR

@Ale1ster Ale1ster changed the title Keysend feature bit Keysend feature bit announcement Feb 18, 2021
@Roasbeef
Copy link
Member

Our main focus right now is deploying AMP, which is a better version of keysend as it supports payment splitting, recurring push payments, a static invoice, and more. We wouldn't be opposed to a PR that adds in their experimental feature bit (though it's odd it's a lower feature bit).

@cfromknecht
Copy link
Contributor

@Ale1ster see my response on the main issue: ElementsProject/lightning#4299 (comment)

The feature bit has not been standardized yet, and as @Roasbeef mentions keysend will be made obsolete in the near term by work on AMP.

@tvolk131
Copy link
Contributor

@ellemouton hey I should have posted something here, but I started on the implementation for this yesterday... If you're already working on it then I'll abandon what I've done, but otherwise I can take this instead. Let me know!

@ellemouton
Copy link
Collaborator

hey @tvolk131 ! i'm about to push up a pr :) review welcome!

@tvolk131
Copy link
Contributor

Sounds good! I just looked it over. I'm a new contributor, and it was reassuring to see that your code was basically identical to mine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants