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 is something we should do whenever possible, as it will be necessary for splicing to have most of the network delay when they consider a channel closed (to allow a new channel_update to come in to notify that the channel was actually just spliced, not closed).
This isn't trivial to do, because we don't have any way of tracking that state yet. We may need to add a new list in Router.Data to track channels that have been spent on chain and are waiting to be either removed or for which we will receive a channel_update with a new funding outpoint (when it was a splice, not a close).
The text was updated successfully, but these errors were encountered:
t-bast
changed the title
Deloy considering a channel closed when seeing an on-chain spend
Delay considering a channel closed when seeing an on-chain spend
Sep 27, 2022
See lightning/bolts#1004
This is something we should do whenever possible, as it will be necessary for splicing to have most of the network delay when they consider a channel closed (to allow a new
channel_update
to come in to notify that the channel was actually just spliced, not closed).This isn't trivial to do, because we don't have any way of tracking that state yet. We may need to add a new list in
Router.Data
to track channels that have been spent on chain and are waiting to be either removed or for which we will receive achannel_update
with a new funding outpoint (when it was a splice, not a close).The text was updated successfully, but these errors were encountered: