Skip to content

[feature]: create new BuildBlindedRoute RPC for the router sub-server #9673

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

Open
Roasbeef opened this issue Apr 2, 2025 · 0 comments
Open
Assignees
Labels
blinded paths enhancement Improvements to existing features / behaviour invoices privacy General label for issues/PRs related to the privacy implications of using the software routing

Comments

@Roasbeef
Copy link
Member

Roasbeef commented Apr 2, 2025

Is your feature request related to a problem? Please describe.

Today it isn't possbile to give lnd a series of pubkeys, then have it create a blinded path blob, assuming that the first node is the introduction point for the route.

Describe the solution you'd like

Add a new BuildBlindedRoute RPC call which implements the above. The logic should automatically look up the various routing policies for each of the nodes to populate the routing policy information for a given routing.BlindedPayment.

A caller should then be able to take the response of the new call, and pass it into an AddInvoice call, which does additional verification, then utilizes the blinded hop information as is.

Describe alternatives you've considered

We could extend the existing BuildRoute for this purpose, but the return values are rather different.

@Roasbeef Roasbeef added blinded paths enhancement Improvements to existing features / behaviour invoices privacy General label for issues/PRs related to the privacy implications of using the software routing labels Apr 2, 2025
@ellemouton ellemouton self-assigned this Apr 5, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blinded paths enhancement Improvements to existing features / behaviour invoices privacy General label for issues/PRs related to the privacy implications of using the software routing
Projects
None yet
Development

No branches or pull requests

2 participants