Olaoluwa Osuntokun [ARCHIVE] on Nostr: 📅 Original date posted:2023-07-16 🗒️ Summary of this message: Lnd supports ...
📅 Original date posted:2023-07-16
🗒️ Summary of this message: Lnd supports paying invoices it generates by setting the `allow_self_payment` field. This can be done through the API provided.
📝 Original message:
lnd supports paying invoices it generates, you just need to set the
`allow_self_payment` field using this
API: https://lightning.engineering/api-docs/api/lnd/router/send-payment-v2.
This _does_ end up actually finding a circular route through the network
though, it's most commonly used to implement circular rebalancing.
However if you set up another node, and then fund bi-lateral "trusted
channels" (so zero conf channel that will never actually confirm as the
funding point will never exist on chain), then you gain the ability to pay
invoices without doing the actual network route. This doesn't need any other
external software, and also gives you all the normal payment/invoice records
you'd expect for normal payments.
Another way to accomplish the same thing would be to use the
`"allow-circular-route` flag, which'll let you double back on the same
channel (incoming+outgoing channel is the same for the route).
-- Laolu
On Sat, Jul 15, 2023 at 8:22 PM fiatjaf <fiatjaf at gmail.com> wrote:
> On Thu, Jul 13, 2023 at 3:47 AM David A. Harding <dave at dtrt.org> wrote:
> > My question is whether you think it would be worthwhile to ask
> > developers of the underlying LN node implementations you use to support
> > self-payment of their own invoices (if they don't already).
>
> As far as I know no Lightning node has this ability, which is very
> unfortunate.
> If possible this should definitely be implemented. It would be the
> biggest feature for custodial Lightning service providers of all kinds
> since always.
> _______________________________________________
> Lightning-dev mailing list
> Lightning-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/lightning-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20230716/7adc6798/attachment.html>
🗒️ Summary of this message: Lnd supports paying invoices it generates by setting the `allow_self_payment` field. This can be done through the API provided.
📝 Original message:
lnd supports paying invoices it generates, you just need to set the
`allow_self_payment` field using this
API: https://lightning.engineering/api-docs/api/lnd/router/send-payment-v2.
This _does_ end up actually finding a circular route through the network
though, it's most commonly used to implement circular rebalancing.
However if you set up another node, and then fund bi-lateral "trusted
channels" (so zero conf channel that will never actually confirm as the
funding point will never exist on chain), then you gain the ability to pay
invoices without doing the actual network route. This doesn't need any other
external software, and also gives you all the normal payment/invoice records
you'd expect for normal payments.
Another way to accomplish the same thing would be to use the
`"allow-circular-route` flag, which'll let you double back on the same
channel (incoming+outgoing channel is the same for the route).
-- Laolu
On Sat, Jul 15, 2023 at 8:22 PM fiatjaf <fiatjaf at gmail.com> wrote:
> On Thu, Jul 13, 2023 at 3:47 AM David A. Harding <dave at dtrt.org> wrote:
> > My question is whether you think it would be worthwhile to ask
> > developers of the underlying LN node implementations you use to support
> > self-payment of their own invoices (if they don't already).
>
> As far as I know no Lightning node has this ability, which is very
> unfortunate.
> If possible this should definitely be implemented. It would be the
> biggest feature for custodial Lightning service providers of all kinds
> since always.
> _______________________________________________
> Lightning-dev mailing list
> Lightning-dev at lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/lightning-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/lightning-dev/attachments/20230716/7adc6798/attachment.html>