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 swap stopped at TakerPaymentWaitConfirmFailed.
taker_swap:1670] !taker_coin.wait_for_confirmations: rpc_clients:158] Waited too long until 1705553666 for transaction to be confirmed 4 times
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.
90741fd42adc056bc8b9dcb2942ce949fff485a2fcc405ed853e31145a11bf98
Both payments are on their chains and locked to the same secret hash a8be0e3a6029a4f791b099faa8e8b4d3b92f8ee8, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 90741fd42adc056bc8b9dcb2942ce949fff485a2fcc405ed853e31145a11bf98
998dd68c5675070a6b0dd89c4f8f6375ed1cdfb5e2226bc03990196e9fdc0fd7
Both payments are on their chains and locked to the same secret hash a8be0e3a6029a4f791b099faa8e8b4d3b92f8ee8, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 2280487ba962be871c78607ef811df76c1e352e9134341a0b71dc5d72a05cd01
- TakerPaymentReceived · TakerPaymentSent: 998dd68c5675070a6b0dd89c4f8f6375ed1cdfb5e2226bc03990196e9fdc0fd7
- TakerPaymentSpent: 0e9ee1ee377202acf89b70ab39cfa4d357445d39968f84b32529432061ecfa25
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.