Bitcoin

Lightning Network – Channel forced closures are broken and their block_til_maturity value is negative. How do I fix it?

One of my colleagues forced the channel to close with me. Several days later, the closure is still pending; blocks_til_maturity The variable goes from positive to negative and continues to add -1 for each block. How is this possible? How do I fix it?

$ lncli pendingchannels
...
"pending_force_closing_channels":  (
        
            "channel":  
                "remote_node_pub":  "02907887f9bfcc9e83512bfdf40ddfdabcb8569786f11ac3e9c52c42d77da3eb6b",
                "channel_point":  "163369b95ee782dc403c11ea33b596c762b98e19bb84826809e536955d38a691:0",
                "capacity":  "116595",
                "local_balance":  "7874",
                "remote_balance":  "105250",
                "local_chan_reserve_sat":  "0",
                "remote_chan_reserve_sat":  "0",
                "initiator":  "INITIATOR_REMOTE",
                "commitment_type":  "ANCHORS",
                "num_forwarding_packages":  "0",
                "chan_status_flags":  "",
                "private":  false,
                "memo":  ""
            ,
            "closing_txid":  "6ada89df0b10973bc82e30148301e13c8ead6683b1decff684c713d2bd13e2d9",
            "limbo_balance":  "8204",
            "maturity_height":  820319,
            "blocks_til_maturity":  -280,
            "recovered_balance":  "0",
            "pending_htlcs":  (),
            "anchor":  "LIMBO"
        
    ),
...

Related Articles

Back to top button