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:273] 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:00:13 UTC.
9bd0bce765105cfb338bc9c407958ea9681c92a827810fe98171ab426b436135
confirmed on-chain
- MakerPaymentSent · MakerPaymentReceived: 9bd0bce765105cfb338bc9c407958ea9681c92a827810fe98171ab426b436135
d11240d7d34ce4a0950db2f859ba8335d57cda5a1956c111cb42dd56c7f94765
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: 891c9690424d3876a014d2ed8bba46ed5023befb20c1d1ba3c2385a61faaa5f8
- TakerPaymentSent · TakerPaymentReceived: d11240d7d34ce4a0950db2f859ba8335d57cda5a1956c111cb42dd56c7f94765
- TakerPaymentSpent: 05e549dcbc8ab69e2862eb67bff4294afe63fb4c9a04f09d0a57c61422615418
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.