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
in recent weeks routing node operators noticed non-routing nodes that establish private & public channels, move sats to the node's local side, and disappear (become inactive). this locks up sats, as the only way to get the sats back is to force close the channel. this negatively impacts the node's routing ability as nodes are unable to use locked-up sats.
add detection of non-routing peers to jet monitor & telegram and notify node operators.
The text was updated successfully, but these errors were encountered:
itsneski
changed the title
add detection of non-routing peers to jet monitor & telegram
feature request: add detection of non-routing peers to jet monitor & telegram
Mar 1, 2022
in recent weeks routing node operators noticed non-routing nodes that establish private & public channels, move sats to the node's local side, and disappear (become inactive). this locks up sats, as the only way to get the sats back is to force close the channel. this negatively impacts the node's routing ability as nodes are unable to use locked-up sats.
add detection of non-routing peers to jet monitor & telegram and notify node operators.
The text was updated successfully, but these errors were encountered: