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 MakerPaymentSpendFailed. The taker's claim on the maker's coin was rejected; it can be retried for as long as that payment is unspent.
taker_swap:2008] "utxo_common:998] utxo_common:950] client:1132] : failed to parse list of 11 headers (coin=CY, from=1369282, 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 says the claim landed: the payment was spent with the preimage, in 95c5bad10d9aebc650c536ba345cea25f53cb9143c255fe554ccc5cfd86f05a8. Checked 2026-10-01 20:30:16 UTC.
989d06ebc9351c63f31818279a6a6a703d5058b49b15c993e137cf0070331d34
confirmed on-chain, locked to this swap's secret hash
- MakerPaymentSent · MakerPaymentReceived: 989d06ebc9351c63f31818279a6a6a703d5058b49b15c993e137cf0070331d34
1690e096ecbfc324deee0f844672cff2c8f065fbc715e4af477f6a66e21d8efb
hash not checked: 4 servers tried: 3 failed TLS verification, 1 refused the connection
- TakerFeeSent · TakerFeeValidated: 878d707c72b61e0cc609a763bfc293fdcccde634b0cf668d2b0e645587999a6c
- TakerPaymentSent · TakerPaymentReceived: 1690e096ecbfc324deee0f844672cff2c8f065fbc715e4af477f6a66e21d8efb
- TakerPaymentSpent: ff848b5b958f9aacd3e0ae4a744045fcb024f66e6dcfc8354a92569f7749f5ba
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.