You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
They were running charge-lnd which had dropped max_htlc to 1 as part of an automated forwarding discouragement strategy for an imbalanced channel.
They had ~200k sats on their side so they thought they would do a 100k sats swap-out test. They forgot about charge-lnd.
Since the maximum htlc size is set to 1 sat the fee prepayment invoice was paid via an unrelated route. See: Pay fee prepayment via explicit route #61 where I argued fee prepayments should be explicitly over the same channel partly as a sanity check.
The swap payment fails to find a route which is expected in this weird scenario.
The unexpected part is it causes CLN peerswap-plugin to crash.
2022-06-03T08:40:42.487Z DEBUG plugin-peerswap-plugin: [FSM] event:id: 6a0fbd775103b48e08ac7bf3e873637cc539442ee1a64d05710fcc62e4a37560, Event_OnSwapOutRequestReceived on
2022-06-03T08:40:42.749Z DEBUG plugin-peerswap-plugin: [FSM] event:id: 6a0fbd775103b48e08ac7bf3e873637cc539442ee1a64d05710fcc62e4a37560, Event_ActionSucceeded on State_SwapOutReceiver_CreateSwap
2022-06-03T08:40:42.749Z INFO plugin-peerswap-plugin: [Swap:6a0fbd775103b48e08ac7bf3e873637cc539442ee1a64d05710fcc62e4a37560] swap out request received: peer: REDACTEDLNDPUBKEY chanId: REDACTEDHEIGHT:REDACTEDINDEX:1 initiator: REDACTEDLNDPUBKEY amount 100000
2022-06-03T08:40:42.752Z DEBUG plugin-peerswap-plugin: [FSM] event:id: 6a0fbd775103b48e08ac7bf3e873637cc539442ee1a64d05710fcc62e4a37560, Event_ActionSucceeded on State_SwapOutReceiver_SendFeeInvoice
2022-06-03T08:40:43.895Z INFO lightningd: Resolved invoice '6a0fbd775103b48e08ac7bf3e873637cc539442ee1a64d05710fcc62e4a37560_fee' with amount 258000msat in 1 htlcs
2022-06-03T08:40:43.902Z DEBUG plugin-peerswap-plugin: [FSM] event:id: 6a0fbd775103b48e08ac7bf3e873637cc539442ee1a64d05710fcc62e4a37560, Event_OnFeeInvoicePaid on State_SwapOutReceiver_AwaitFeeInvoicePayment
2022-06-03T08:40:45.369Z DEBUG plugin-peerswap-plugin: [FSM] event:id: 6a0fbd775103b48e08ac7bf3e873637cc539442ee1a64d05710fcc62e4a37560, Event_ActionSucceeded on State_SwapOutReceiver_BroadcastOpeningTx
2022-06-03T08:40:45.369Z DEBUG plugin-peerswap-plugin: [RedundantSender]\tstart sending messages of type 42077 to REDACTEDLNDPUBKEY
2022-06-03T08:40:45.369Z DEBUG plugin-peerswap-plugin:
2022-06-03T08:40:45.372Z DEBUG plugin-peerswap-plugin: [FSM] event:id: 6a0fbd775103b48e08ac7bf3e873637cc539442ee1a64d05710fcc62e4a37560, Event_ActionSucceeded on State_SwapOutReceiver_SendTxBroadcastedMessage
2022-06-03T08:44:36.676Z DEBUG plugin-peerswap-plugin: [Messenger] From: REDACTEDLNDPUBKEY got msgtype: a461 payload: {\"swap_id\":\"6a0fbd775103b48e08ac7bf3e873637cc539442ee1a64d05710fcc62e4a37560\",\"message\":\"could not pay invoice, last err payment failure FAILURE_REASON_NO_ROUTE\",\"privkey\":\"cf22815b60f825e73c0cecd932232f28459e4da207e4eab47fb8eb7a748ba456\"}
2022-06-03T08:44:36.689Z DEBUG plugin-peerswap-plugin: [FSM] event:id: 6a0fbd775103b48e08ac7bf3e873637cc539442ee1a64d05710fcc62e4a37560, Event_OnCoopCloseReceived on State_SwapOutReceiver_AwaitClaimInvoicePayment
2022-06-03T08:44:36.689Z DEBUG plugin-peerswap-plugin: [RedundantSender]\tstop sending messages of type 42077 to REDACTEDLNDPUBKEY
2022-06-03T08:44:36.689Z DEBUG plugin-peerswap-plugin:
2022-06-03T08:44:37.236Z INFO plugin-peerswap-plugin: Killing plugin: exited during normal operation
@wtogami since 6135d8d we have a nil check to at least avoid a panic.
Maybe we can close this for now, we still have it documented here and can reopen in the case that this happens again or if we have a better solution at some point.
CLN v0.10.2 PeerSwap 2833bdb
LND v0.14.1-beta PeerSwap 1f0e91f
LND requested lbtc swap-out from CLN. Swap payment failed to find a route and we know it was the LND node's fault. How?
https://github.com/accumulator/charge-lnd
swap-out
test. They forgot about charge-lnd.peerswap-panic-log
The text was updated successfully, but these errors were encountered: