-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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 creation of custom macaroons #3516
Comments
I'd say that establishing a direct connection to your payment destination is not ideal and doesn't scale. Why does this only apply to Neutrino?
Mixing peer permissions with invoices for an invoice macaroon doesn't seem like a nice separation of concerns to me, which is what the macaroons attempt to achieve at the moment. Either a peer macaroon should exist, or you can create your own custom macaroon once that's supported. |
Doesn't only apply to neutrino (we can think corporate firewall issues as an example), but neutrino is a good example. Peer macaroon would be perfect. Saying that Is there any timeline for support for custom macaroons? Would LL be up for reviewing a PR for a |
I think we'd rather opt for a more generalized bakery vs adding new macaroons for specific use cases. |
connectPeer
permissions to invoice macaroon
Fixed by #1160 |
Background
connectPeer
requires access to the admin macaroon, however if a user needs to make payments and is using neutrino, the best way to establish connections through peers is to useconnectPeer
and then they can open a channel to your node.I want to be able to use the
connectPeer
API without requiring the admin macaroon and invoice macaroon seems like a good interim place to put this before custom macaroons is released.The text was updated successfully, but these errors were encountered: