This one took about 8.6× the usual for LCC/RVN. Waiting longer than usual is not in itself a failure: a swap waits on confirmations from both chains, and a slow block or a busy network stretches it.
The record stops at TakerPaymentSpendFailed. The maker's claim on the taker's coin was rejected; it can be retried for as long as that payment is unspent.
maker_swap:1269] !taker_coin.send_maker_spends_taker_payment: mm2src\coins\utxo\ "utxo_common:998] utxo_common:950] client:1132] : failed to parse list of 11 headers (coin=RVN, from=4489286, requested_count=11): UnexpectedEnd"
By this step both payments were on their chains and the price had been struck, so the trade counts toward the reference price. The claim can still be made for as long as the payment is unspent, and since the timelock has passed the payer can take it back as well, so whichever lands first settles it. Whether it was retried is a question for the chain rather than for this log.
The chain shows the taker's payment still sitting in its contract: neither claimed nor refunded. The maker never collected, so the secret was not revealed and the timelock expired 2026-08-08 18:07:56 UTC, so the taker can take it back now. Checked 2026-11-06 01:44:27 UTC. It will be asked again.
Wondering whether this one is yours? SwapScope cannot tell you: the parties are salted hashes, so that nobody can test a key against this data, and that cuts both ways. Search this swap's uuid in your own wallet's swap history, or open the payment transaction above on a block explorer and see whether the address paying into it is one of yours.
925759144909c1ee84af5f789ace14fd63ba68cfb297452763e95407ea1c8e68
confirmed on-chain, locked to this swap's secret hash
- MakerPaymentSent · MakerPaymentReceived: 925759144909c1ee84af5f789ace14fd63ba68cfb297452763e95407ea1c8e68
- MakerPaymentRefunded: 9e61f9cb10dceb28da77f9085a1a1df4d26a9d799626cd0555480370b4724060
e04546754e34c77621eedce2fd1e81097342e4b6a2fdda1481fb40030edeaf8e
confirmed on-chain, locked to this swap's secret hash
- TakerFeeSent · TakerFeeValidated: 835922a641a46b77a5f1137a923c0537e2a4c4182ddba940724330086ad5293c
- TakerPaymentSent · TakerPaymentReceived: e04546754e34c77621eedce2fd1e81097342e4b6a2fdda1481fb40030edeaf8e
- TakerPaymentRefunded: 50f05b448c02b00e149d62c1c7ff809f3c0dd67c1b72347e030004437eba42c8
No flags are stored against this swap. Flags are written while a swap sits inside a live pricing window, so on an older swap their absence means it was never assessed rather than that it was assessed and found clean.
Reported by kdf-statsdb-8762.