[go: nahoru, domu]

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

Support blinded paths (i.e. bolt12) in renepay #6609

Open
rustyrussell opened this issue Aug 24, 2023 · 1 comment
Open

Support blinded paths (i.e. bolt12) in renepay #6609

rustyrussell opened this issue Aug 24, 2023 · 1 comment
Assignees

Comments

@rustyrussell
Copy link
Contributor

We use localmods to do this:

  1. If no blinded path uses the destination node itself as an entry point: remove/disable all other channels into the node.
  2. Add blinded paths as "channels" in the graph.

When we use a blinded hop, catch it at sendpay creation time and insert multiple hops. This might require additional args to sendpay, or switching to sendonion?

@rustyrussell rustyrussell added this to the v23.11 milestone Aug 24, 2023
@rustyrussell rustyrussell self-assigned this Aug 24, 2023
@nepet nepet removed this from the v23.11 milestone Dec 3, 2023
@Lagrang3
Copy link
Collaborator
Lagrang3 commented Aug 6, 2024

I am working on this. First thing to add blinded path arguments to sendpay (#7493), then re-engineer a little bit renepay's MCF solver to send a payment to multiple destinations (one for each blinded path entry node) .
Still to think about how to handle multiple blinded paths with the same entry node and the special case when the entry node is ourselves.

To generate all sorts of blinded path special cases for testing we would need some RPC to generate arbitrary blinded paths, because currently the only way to obtain one is through offer->fetchinvoice and CLN will automatically generate one, not multiple and very trivial single node path.

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

No branches or pull requests

3 participants