pull down to refresh

What's worse is there is another bug in .8 that will crash the onchaind and make jam the channel too. I posted the trace yesterday. I'm still trying to work out what happened here and why its crashing.

Check for "ONCHAIN:Owning subdaemon onchaind died" in the listpeerchannels, however after 100 blocks core lightning will discard it.

.8 cannot recover the left over funds from the force close either -
I would strongly recommend folks disable new channels on core lightning until that crash of onchaind is fixed. There is active exploitation of this --

02512b218bb367eb09464b101f3d98a83f1dcf8022e7f28a9010fe1c0022c8f8a9 hit my node with this, and I cannot get onchaind in .8 to read its state.

reply

And the attacker has swept 'my side' of the stale commitment transaction force closes.

reply