So this is a result of a payment either getting stuck or currently in flight.
{ "attempt_id": "7", "status": "IN_FLIGHT", "route": { "total_time_lock": 775227, "total_fees": "570", "total_amt": "271796", "hops": [ { "chan_id": "852010460957179905", "chan_capacity": "500000", "amt_to_forward": "271795", "fee": "1", "expiry": 775187, "amt_to_forward_msat": "271795032", "fee_msat": "1271", "pub_key": "03cc1d0932bb99b0697f5b5e5961b83ab7fd66f1efc4c9f5c7bad66c1bcbe78f02", "tlv_payload": true, "mpp_record": null, "amp_record": null, "custom_records": { } },
The important number here is "expiry": 775187, which is the max block it'll be stuck for, which is about 200 blocks from now or around ~30 or so hours from now.
Best case scenario, it gets unstuck before then. It is typical that the payment is in flight for the duration of the loop out period, which takes 2 on chain transactions. Make sure you don't turn off your node for this portion. If all went well, eventually you'll have that in flight payment show as successful and you will have some on chain funds.
Worst case, the payment is acttually stuck and it'll result in a unilateral (force) close where you will be able to get the funds back, but on chain as a result of closing the channel. After the channel closes, it'll take a bit more time after that to actually spend the funds, since your channel partner will have a chance to reveal the preimage still.
Payments getting stuck is no fun, and unilateral closures aren't either, but that's part of the protocol when a spontanous failure occurs down the line. As long as you don't turn off your node, you should have your funds back, either on chain or back in the channel. It's just that at most it could take 7 - 10 days, but hopefully less than 2.
Edit:
You probably didn't do anything wrong here and it was a result of a payment failure down the line. Though you could ask @k00b if it shows that he has the same payment stuck but on the other side. If so, then yeah it wasn't your fault. But there's a chance there's a communication problem between you and k00b in which case it could be your fault (or tor's fault).
Thank you for your reply! Guess will wait 7-10 days and see what happens!
reply