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 MakerPaymentSpendConfirmFailed. The taker's claim on the maker's coin was broadcast but not seen to confirm.
taker_swap:2050] !wait for maker payment spend confirmations: rpc_clients:119] Waited too long until 1770362320 for transaction to be confirmed 2 times
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 be retried for as long as the payment is unspent, and until the timelock passes nobody else can touch 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 ca834b67077319b9d077e250abeeded50648731944d05f7d425bae0b86a9c397. Checked 2026-10-01 19:10:25 UTC.
a5dae28e019978c5b05c27240e9ded57a7c93a081ccd1dcba228ef324168cd66
ARRR settles as ZHTLC, 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
- MakerPaymentReceived: a5dae28e019978c5b05c27240e9ded57a7c93a081ccd1dcba228ef324168cd66
- MakerPaymentSpent: ca834b67077319b9d077e250abeeded50648731944d05f7d425bae0b86a9c397
d714338b14800998928060a583aaa9deaff1282777de445ced95cfa09bfe1954
confirmed on-chain, locked to this swap's secret hash
- TakerFeeSent: 7166f02a9b203f76a88c5ae6c90f6c70239026a5170dabf4701bd590c45cd2e3
- TakerPaymentSent: d714338b14800998928060a583aaa9deaff1282777de445ced95cfa09bfe1954
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.