[ad_1]
I seen that almost all of my lightning funds fail regardless of growing the charge. It has been like this during the last two months.
Investigating this matter, I discovered an inactive channel within the output of listpeerchannels
:
"peer_id": "03864ef025fde8fb587d989186ce6a4a186895ee44a926bfc370e2c366597a3f8f",
"peer_connected": true,
"reestablished": false,
"channel_type":
"bits": [
12,
22,
46
],
"names": [
"static_remotekey/even",
"anchors/even",
"scid_alias/even"
]
,
"updates":
"native":
"htlc_minimum_msat": 1,
"htlc_maximum_msat": 7549746000,
"cltv_expiry_delta": 34,
"fee_base_msat": 1000,
"fee_proportional_millionths": 10
,
"last_stable_connection": 1721499560,
"state": "AWAITING_UNILATERAL",
"scratch_txid": "991419d10eb2f1f01596e68eac18dafcb34b24ff7a03e21936a739c4128cd460",
"last_tx_fee_msat": 2888000, (my be aware: Saturday, 20 July 2024 18:19:20 GMT)
"lost_state": false,
"feerate":
"perkw": 2276,
"perkb": 9104
,
"path": 0,
"channel_id": "881895f720246c99b6d4d9278510d37370344239e2e235f5e61c792ec495ea0e",
"funding_txid": "0eea95c42e791ce6f535e2e23942347073d3108527d9d4b6996c2420f7951888",
"funding_outnum": 0,
"close_to_addr": "bc1pv5jzxk7h60ea3wnk4a92yxjufdyj7689fc936yn0ln5d7q4ykwnsc46cgf",
"close_to": "51206524235bd7d3f3d8ba76af4aa21a5c4b492f68e54e0b1d126ffce8df02a4b3a7",
"non-public": true,
"opener": "native",
"alias":
"native": "740013x9434280x28179"
,
"options": [
"option_static_remotekey",
"option_anchors_zero_fee_htlc_tx",
"option_anchors",
"option_scid_alias"
],
"funding":
"local_funds_msat": 16777215000,
"remote_funds_msat": 0,
"pushed_msat": 0
,
"to_us_msat": 16777215000,
"min_to_us_msat": 16777215000,
"max_to_us_msat": 16777215000,
"total_msat": 16777215000,
"fee_base_msat": 1000,
"fee_proportional_millionths": 10,
"dust_limit_msat": 546000,
"max_total_htlc_in_msat": 18446744073709551615,
"their_reserve_msat": 167772000,
"our_reserve_msat": 167772000,
"spendable_msat": 16602238000,
"receivable_msat": 0,
"minimum_htlc_in_msat": 0,
"minimum_htlc_out_msat": 1,
"maximum_htlc_out_msat": 7549746000,
"their_to_self_delay": 144,
"our_to_self_delay": 720,
"max_accepted_htlcs": 30,
"state_changes": [
"timestamp": "2024-07-20T18:20:19.887Z",
"old_state": "CHANNELD_AWAITING_LOCKIN",
"new_state": "AWAITING_UNILATERAL",
"cause": "protocol",
"message": "channeld: received ERROR channel 881895f720246c99b6d4d9278510d37370344239e2e235f5e61c792ec495ea0e: unknown channel"
],
"standing": [
"Loaded from database"
],
"in_payments_offered": 0,
"in_offered_msat": 0,
"in_payments_fulfilled": 0,
"in_fulfilled_msat": 0,
"out_payments_offered": 0,
"out_offered_msat": 0,
"out_payments_fulfilled": 0,
"out_fulfilled_msat": 0,
"htlcs": []
I’ve no use of this channel and so I attempted to shut it,
sudo lightning-cli shut 881895f720246c99b6d4d9278510d37370344239e2e235f5e61c792ec495ea0e
returned
"code": -32602,
"message": "id: Channel id not discovered: invalid token (see logs for particulars)"
Over the past months I tried to profit from low charges by opening
lightning channels paying 2-3 sats/vbyte in charges. I did it over poor, intermittent connectivity, and
I used to be steadily shutting down my node whereas the funding transaction was nonetheless unconfirmed.
I’ve non-public channels, 6 with ACINQ’s node and 1 with ALLNICE | TORQ.co.
From what I gathered from the values of last_stable_connection
and timestamp
(of the final state change)
the channel was force-closed earlier than it was locked-in with six confirmations. But,
it has been per week because the inactive channel and there
is no historical past of any transaction involving close_to_addr
.
1. What does standing Loaded from database
imply and why is the channel known as unknown
?
2. Can or not it’s that my node was flagged by ACINQ node after this force-closure was triggered.
May this the reason for the failure of my funds?
3. Ought to I do something about it? How a lot sats am I going to unfastened with this
force-closure?
4. How may I stop related points from taking place sooner or later?
[ad_2]
Supply hyperlink
Leave a Reply