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:1172] !taker_coin.send_maker_spends_taker_payment: utxo_common:1682] HTLC spend fee 24930563 is greater than transaction output 22947964
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-10-22 14:43:06 UTC, so the taker can take it back now. Checked 2026-11-06 05:04:48 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.
e8adb7cdd7b8ca2781f6a90822ebd8da9705dd0a19324c3895092712cb5e6804
confirmed on-chain, locked to this swap's secret hash
- MakerPaymentSent · MakerPaymentReceived: e8adb7cdd7b8ca2781f6a90822ebd8da9705dd0a19324c3895092712cb5e6804
- MakerPaymentRefunded: bf08ff287aea83b24507966d4b9d96cb07b29a4efd34517056bf803d5602e1dd
0dfadcc6f601c65b724d13d28f70f0746fb4a24eec8f9c2d06d4737e86a3b8a8
confirmed on-chain, locked to this swap's secret hash
- TakerFeeSent · TakerFeeValidated: 4c2d4f607348dc76e52793389239addd20bdd5c9e69f025e30ea628e9f9fdae4
- TakerPaymentSent · TakerPaymentReceived: 0dfadcc6f601c65b724d13d28f70f0746fb4a24eec8f9c2d06d4737e86a3b8a8
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.