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 Feb 12, 2025. It is now read-only.
Eclair app is a special case of LN node in a sense that it never routes third party payments so in case when expired outgoing HTLC payments are present it may not close a channel automatically because an expired HTLC is guaranteed to be locally initiated, so there is no risk of waiting and losing money downstream.
Instead of closing a channel right away an app may show a warning and recommendation to contact a faulty peer owner to resolve this without closing a channel. The benefit of this approach is that it saves time and money and makes app behavior more predictable: currently, when sending each payment an expirienced user knows there is a risk of channel closing because of that payment getting stuck which is quite terrible UX wise.
The text was updated successfully, but these errors were encountered:
Eclair app is a special case of LN node in a sense that it never routes third party payments so in case when expired outgoing HTLC payments are present it may not close a channel automatically because an expired HTLC is guaranteed to be locally initiated, so there is no risk of waiting and losing money downstream.
Instead of closing a channel right away an app may show a warning and recommendation to contact a faulty peer owner to resolve this without closing a channel. The benefit of this approach is that it saves time and money and makes app behavior more predictable: currently, when sending each payment an expirienced user knows there is a risk of channel closing because of that payment getting stuck which is quite terrible UX wise.
The text was updated successfully, but these errors were encountered: