Open TonyGiorgio opened 1 year ago
Mh this stage, so in this issue there is two sub-issue:
new fee rate 0.00001006 BTC/kvB <= old fee rate 0.00001006 BTC/kvB.
? If I am able to do the math 0.00001006 == 0.00001006
.Mh! ok looks like our multi-funding channel RPC is a chain of callback, so the error is through by Bitcoin core not core lightning,
Core lightning cannot backtrack during the error and update remove the channel from the listfunds
. The channel should never be open because the funding transaction died before,
So no funding lost. But I should spend more time debugging it this week.
So no funding lost
Funds were lost, because the funding transaction was never broadcasted on the 0 conf channel.
Ah right we are in a 0-conf, my bad :)
Was minconf=0
used when opening the 0 conf channel?
We're having similar problem at Alby with 0 conf channels when using minconf=0
Issue and Steps to Reproduce
fundchannel
and get this weird broadcast error for no logical reasonThis will result in loss of funds for the other peer once it closes. There's no attempt to rebroadcast the transaction or mark the channel as invalid despite the failure to the
fundchannel
rpc.After awhile when I noticed this, I broadcasted the transaction hex manually. I don't see any reason why it was getting the obscure broadcast error. But regardless, it should not consider the channel valid if the RPC fails.
getinfo
outputhttps://mutinynet.com/tx/43e2bce5eb841c5e1f0015e9f384ab3a00973e7497489ac8f5019224aea1061b