--- Log opened Fri Dec 22 00:00:07 2023
00:22 -!- jon_atack [~jonatack@user/jonatack] has quit [Read error: Connection reset by peer]
00:22 -!- jonatack [~jonatack@user/jonatack] has joined #c-lightning
01:43 -!- jespada [~jespada@cpc121308-nmal25-2-0-cust15.19-2.cable.virginm.net] has joined #c-lightning
08:58 -!- jespada [~jespada@cpc121308-nmal25-2-0-cust15.19-2.cable.virginm.net] has quit [Quit: Textual IRC Client: www.textualapp.com]
14:44 -!- Guest61 [~Guest61@99-116-235-190.lightspeed.austtx.sbcglobal.net] has joined #c-lightning
14:45 < Guest61> I am the person who was in here a few days ago complaining about c-lightning. I wanted to follow up for the record (since these chats are logged)
14:46 < Guest61> 1. to give an update and inform that after latest update, the newest version hotfix release of clightning, no more issues
14:46 < Guest61> 2. to give report on my experience with the solution in case if other experienced the same
14:47 < Guest61> I don tknow what the issues were with unreliability of chan opening/closings, if the newest update was even realted or not. i just know it is reliable again after updateing
14:48 < Guest61> for the funds i thought were lost, i was able to export the private key, (xpriv) from the HSM file. I imported into sparrow wallet using m/0 as derivation path, and checked BOTH native segwit and taproot addresses. I was able to recover funds this way
14:49 < Guest61> for a second issue, i did not see funds from a forced chan closure, that is because i think the output from the forced unilateral close was to a script output rather than standard btc address. but it would never confirm because fee was too low, 2 sats per byte. fee on the unilateral close was too low because i made a typo when selecting a fee size.
14:49 < Guest61> for that, since rbf and cpfp was not an option.... i used a "tx accelerator" service to pay miners out of band to get the transaction confirmed next block
14:51 < Guest61> thanks devs, for what you do. core lightning in my opinion, is the best implementation for lightning
14:52 < Guest61> i hope if others have this same issue, that they will come across this information
14:55 -!- Guest61 [~Guest61@99-116-235-190.lightspeed.austtx.sbcglobal.net] has quit [Quit: Client closed]
20:51 -!- jonatack [~jonatack@user/jonatack] has quit [Read error: Connection reset by peer]
20:52 -!- jonatack [~jonatack@user/jonatack] has joined #c-lightning
--- Log closed Sat Dec 23 00:00:07 2023