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 1705810208 for transaction to be confirmed 3 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.
68bfb2eed9cfd0c8d1fb7ce04963224a83b5e6a2eeed2ce71667658dd09e1db5
Both payments are on their chains and locked to the same secret hash 6caf26d5e041520081eb24861899b51197074b9c, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 68bfb2eed9cfd0c8d1fb7ce04963224a83b5e6a2eeed2ce71667658dd09e1db5
8e1d1c2e1c9e9a8d98256a10fb4dd9779c2e92addd5fb8dd0f86061b9dc69eed
Both payments are on their chains and locked to the same secret hash 6caf26d5e041520081eb24861899b51197074b9c, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: ca9d65a955fd92f9f0073e090c06cb40f875f19c0931eb522efecece84d37765
- TakerPaymentSent · TakerPaymentReceived: 8e1d1c2e1c9e9a8d98256a10fb4dd9779c2e92addd5fb8dd0f86061b9dc69eed
- TakerPaymentSpent: a971110c46fd333142147f3a8fb89e70dad6b1947f637a0622ccb103802855ef
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.