An atomic swap is not instant by design. Each side has to publish a transaction and wait for the other chain to confirm it, so the time it takes is set mostly by the block spacing of the two chains involved rather than by anything either party does.
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:1114] !taker_coin.send_maker_spends_taker_payment: utxo_common:1607] HTLC spend fee 15337523 is greater than transaction output 11225952
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 2025-12-15 02:09:10 UTC, so the taker can take it back now. Checked 2026-11-06 04:49:16 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.
55d35def55e41e6b6d4a539fc2e87ef0b9e574ecf8f1ec1e031c4571220f0897
confirmed on-chain, locked to this swap's secret hash
- MakerPaymentReceived · MakerPaymentSent: 55d35def55e41e6b6d4a539fc2e87ef0b9e574ecf8f1ec1e031c4571220f0897
- MakerPaymentRefunded: 3ec7e27332d0387f04593dfdd1816ec6f0e1205c191903ce4c6a4e6bbfe9b1c5
4e2edbeac2630c6408d05d3466c54355ddd5218e2b2ce20eb44e91d85e43506b
confirmed on-chain, locked to this swap's secret hash
- TakerFeeSent · TakerFeeValidated: 77172543e62caf90cb6d2222f1a809ce4c102261c2e9d2ccbbc1ea042fc8a4df
- TakerPaymentSent · TakerPaymentReceived: 4e2edbeac2630c6408d05d3466c54355ddd5218e2b2ce20eb44e91d85e43506b
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.