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 1705810124 for transaction to be confirmed 2 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.
ea41d13257b04bf6518a698e2fef00eb8f88747f48ed0931fdffd2d40abea66d
Both payments are on their chains and locked to the same secret hash 01cfe1cd664b4920cde7f938fcd3d5b062e75764, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: ea41d13257b04bf6518a698e2fef00eb8f88747f48ed0931fdffd2d40abea66d
ed43cfec6b80fa6fd23eb781cc58684df709dfa06893e2c60ba9f2a02c7161d1
Both payments are on their chains and locked to the same secret hash 01cfe1cd664b4920cde7f938fcd3d5b062e75764, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 494be70c7b616f26d2bf2ada19964a070c2df06c8cf7e6146bac31110a3f54b2
- TakerPaymentSent · TakerPaymentReceived: ed43cfec6b80fa6fd23eb781cc58684df709dfa06893e2c60ba9f2a02c7161d1
- TakerPaymentSpent: 1992a5b15a93f7ce6c32da01c136aadf0227cb038aad330aa884c26c04a683e9
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.