Peer Initiated Swaps Fail

[NodeMacD]

All peer initiated (incoming) swaps to my node result in failed state. However, swaps initiated by me are typically successful (outgoing).

Latest example log:
2026/05/22 16:38:47 [INFO] PeerSwap LND starting up with commit 8f67039
...
2026/05/22 16:41:15 [INFO] [MsgListener]: Start listening for custom messages
2026/05/22 16:41:15 [INFO] peerswapd grpc listening on localhost:42069
2026/05/22 16:41:15 [INFO] peerswapd rest listening on localhost:42070
2026/05/27 16:48:02 [INFO] [Swap:3ae86610a8b28e3958a5f3ee594c00f63d5c4c00af77f145589b6eefb443b44a] swap-in request received: peer: 03c8e5f583585cac1de2b7503a6ccd3c12ba477cfd139cd4905be504c2f48e86bd chanId: 949881:2268:1 initiator: 03c8e5f583585cac1de2b7503a6ccd3c12ba477cfd139cd4905be504c2f48e86bd amount 3286723
2026/05/27 16:58:02 [INFO] [Swap:3ae86610a8b28e3958a5f3ee594c00f63d5c4c00af77f145589b6eefb443b44a] Swap claimed cooperatively
2026/05/27 17:09:07 [INFO] block watcher: lbtc, server returned HTTP error 503
2026/05/27 17:11:59 [INFO] block watcher: reconnected to lbtc daemon

@ronballesteros i've been instructed to ask you to add your logs.

[YusukeShimizu]

Thanks for sharing the logs. From the snippet alone, this swap does not look like it reached a failed terminal state.

Swap claimed cooperatively corresponds to State_ClaimedCoop, which is a completed state in PeerSwap. It does not mean State_SwapCanceled. However, it also means the swap completed through the cooperative close path rather than the normal preimage-claim path.

The cooperative close path is a fallback/cleanup path used when the normal flow cannot or should not continue, for example due to a timeout, cancel, claim invoice payment failure, temporary backend/RPC issue, or being too close to the CSV safety window after restart/recovery.

So based only on this log, It looks like it completed cooperatively. What we need to understand is why it entered the cooperative close path.