chantools doesn't have great support for core lightning. I ran sweepremoteclosed but it didnt find anything at all with all the attacker public keys. I also tried it with a legit channel that I am waiting to timeout to claim a force close. It found nothing -- not even that there was a cooldown and could be claimed later.
I notice the attacker has not claimed the remainder of the channel, so I should at least be able to claw the old state balance back. The node has 'dropped' all references to these txs after 100 blocks. What I am seeing in all the attacker force closes is an old state, and my node got confused and was not able to broadcast the justice transactions. The client reported that it did, but the node got confused and dropped the references in listpeerchannels.
I am concerned that there are more attacker transactions that I have missed.
There is one pending local close with a large cooldown (1000 blocks) that I was hoping to try to recover with this tool, but it doesn't look like this will work. I might have to fire up the node in a week to sweep that one.
I might be able to derive something with hsmtool?
Core Lightning appears to be missing some essential tools that allow recovery from the database+hsm when the cheating transaction is sent via a force close.
chantools doesn't have great support for core lightning. I ran sweepremoteclosed but it didnt find anything at all with all the attacker public keys. I also tried it with a legit channel that I am waiting to timeout to claim a force close. It found nothing -- not even that there was a cooldown and could be claimed later.
I notice the attacker has not claimed the remainder of the channel, so I should at least be able to claw the old state balance back. The node has 'dropped' all references to these txs after 100 blocks. What I am seeing in all the attacker force closes is an old state, and my node got confused and was not able to broadcast the justice transactions. The client reported that it did, but the node got confused and dropped the references in listpeerchannels.
I am concerned that there are more attacker transactions that I have missed.
There is one pending local close with a large cooldown (1000 blocks) that I was hoping to try to recover with this tool, but it doesn't look like this will work. I might have to fire up the node in a week to sweep that one.
I might be able to derive something with hsmtool?
Core Lightning appears to be missing some essential tools that allow recovery from the database+hsm when the cheating transaction is sent via a force close.