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.
Nothing was lost. The payment was never claimed: it was spent without the preimage, after the timelock, which is the refund path back to the payer, in 12e9adf2e8074b07562181761e07e911d9bfee2d5b0cec044f2fe3ecd8785716.
The swap stopped 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=4475406, requested_count=11): UnexpectedEnd"
Recorded by the swap's own protocol log, which is the only source that knows: the aggregator reports failed and completed swaps identically. Nothing changed hands, so it sets no reference price.
dd7a5c0ec6fc123b5af3a05d6221fb24967c0d594acd745fcbff9f304a89b2dc
confirmed on-chain, locked to this swap's secret hash
- MakerPaymentSent · MakerPaymentReceived: dd7a5c0ec6fc123b5af3a05d6221fb24967c0d594acd745fcbff9f304a89b2dc
- MakerPaymentRefunded: bd0d0a09f5eab252fd46af2cdf31fefae297f86d67b76b5d4ab917b179824e69
d18c0eaf9c778b18f3a5b66835d91ebc9d67a2de6464c470c6e6eb49e8505c00
confirmed on-chain, locked to this swap's secret hash
- TakerFeeSent · TakerFeeValidated: d7871c6998050e90cac7067519689154c31aa59e3850aee9e64e6968e238a6e1
- TakerPaymentSent · TakerPaymentReceived: d18c0eaf9c778b18f3a5b66835d91ebc9d67a2de6464c470c6e6eb49e8505c00
- TakerPaymentRefunded: 12e9adf2e8074b07562181761e07e911d9bfee2d5b0cec044f2fe3ecd8785716
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.