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
This issue serves as a place for discussing whether we should remove AutoSettle. It requires additional code paths, and arguably the added value is only in testing/development. The intended user group for lnmux is unlikely to need this functionality.
Alternatively it can be implemented in a script that subscribes to all payments via SubscribeInvoiceAccepted and automatically calls SettleInvoice for each of them.
The text was updated successfully, but these errors were encountered:
Wouldn’t it useful for people that will use lnmux as a virtual node? (for inbound fees for example)
Maybe they won't want to rework their existing architecture to subscribe to lnmux events, but just use it as a virtual node
But for that, it is necessary to have a RPC call to retrieve all paid invoices (as there will be no settlement notifications). (see this issue)
This issue serves as a place for discussing whether we should remove
AutoSettle
. It requires additional code paths, and arguably the added value is only in testing/development. The intended user group for lnmux is unlikely to need this functionality.Alternatively it can be implemented in a script that subscribes to all payments via
SubscribeInvoiceAccepted
and automatically callsSettleInvoice
for each of them.The text was updated successfully, but these errors were encountered: