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:1727] utxo_common_swap:271] MmError { etype: IguanaPrivKeyUnavailable, trace: [TraceLocation { file: "lp_coins_context", line: 279 }] }
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.
This payment cannot be read on its chain yet. Checked 2026-10-01 14:10:07 UTC.
1651330dd4ad62034e8d711004f27e0f7d8c430e1fd9f25443e366972c6401a0
confirmed on-chain
- MakerPaymentSent · MakerPaymentReceived: 1651330dd4ad62034e8d711004f27e0f7d8c430e1fd9f25443e366972c6401a0
c1c501034ed4bae0663e0ec400ea088202e1997e3f754aa65c13c3a2a492db37
SC settles as SIA, whose transfers do not appear as an output any chain server can read, so the transaction the record names cannot be checked against a chain here
- TakerFeeSent · TakerFeeValidated: 8ff79dd317e239b46bf3a05227e6696db226c6bd5dbadfef41fe994b2b9a1d19
- TakerPaymentSent · TakerPaymentReceived: c1c501034ed4bae0663e0ec400ea088202e1997e3f754aa65c13c3a2a492db37
- TakerPaymentSpent: b22ec415908e53fc757434b07f265d26e01e3dd63e3cb6cd7fb9d89fe2e16e15
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.