You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 2, 2024. It is now read-only.
Hey there
I installed NWC next and connected it to my Alby account. So far so good, amazing job 🎉
At the moment I only have one private channel. If I then use my Alby Lightning Address to resolve an invoice it does not contain route hints. That invoice will be useless because no one in the network will find a route to my private node.
Would it make sense to include the --private parameter to the addInvoice RPC call to include route hints per default? I have seen that this used to be enabled by default by lnd, but then removed because of privacy considerations. Now one has to actively opt-in to include route hints.
Alternatively, the flag could be set only if all channels are private.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hey there
I installed NWC next and connected it to my Alby account. So far so good, amazing job 🎉
At the moment I only have one private channel. If I then use my Alby Lightning Address to resolve an invoice it does not contain route hints. That invoice will be useless because no one in the network will find a route to my private node.
Would it make sense to include the
--private
parameter to theaddInvoice
RPC call to include route hints per default? I have seen that this used to be enabled by default by lnd, but then removed because of privacy considerations. Now one has to actively opt-in to include route hints.Alternatively, the flag could be set only if all channels are private.
The text was updated successfully, but these errors were encountered: