@litch reports: I'm testing this in a mixed-nodes environment and it looks like a post-spliced channel is un-detectable by LND. I'm not 100% sure why at this point, and have some logs I can provide on request.
Workflow:
- Lnd1 is connected to cln1
- Open a channel between cln1 and cln2
- Verify that Lnd1 can see the channel between cln1 and cln2 in its
describegraph
- Splice the channel
- the channel between cln1 and cln2 is now not listed in the
describegraph
- Open a new channel between cln1 and cln2
- Verify that the new channel between cln1 and cln2 appears in the
describegraph, whereas the spliced one does not
Happy to help debug!
EDIT TO ADD:
It looks the newly-created channel eventually does get broadcast. The ChannelAnnounce message wound up getting broadcast an hour after the splice happened. Even with dev-fast-gossip enabled and I restarted the CLN node within that hour window (at about 40 minutes). Unsure if that is related.
In any case: tACK (at least in my cluster of regtest nodes)
Originally posted by @litch in #6253 (comment)
@litch reports: I'm testing this in a mixed-nodes environment and it looks like a post-spliced channel is un-detectable by LND. I'm not 100% sure why at this point, and have some logs I can provide on request.
Workflow:
describegraphdescribegraphdescribegraph, whereas the spliced one does notHappy to help debug!
EDIT TO ADD:
It looks the newly-created channel eventually does get broadcast. The ChannelAnnounce message wound up getting broadcast an hour after the splice happened. Even with dev-fast-gossip enabled and I restarted the CLN node within that hour window (at about 40 minutes). Unsure if that is related.
In any case: tACK (at least in my cluster of regtest nodes)
Originally posted by @litch in #6253 (comment)