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 1705958800 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.
5ca19c913ad27eb657e1d0c15ae4f7e4fde5c2cdfcc556d767f357cae44dcc19
Both payments are on their chains and locked to the same secret hash c352f24d5df88d2ab45039f6fa7e1ff7419d9cf0, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 5ca19c913ad27eb657e1d0c15ae4f7e4fde5c2cdfcc556d767f357cae44dcc19
8cc5c24d6edb5d87086e27ac422a3a05e9d866b04590017c6f8523bc82bcb919
Both payments are on their chains and locked to the same secret hash c352f24d5df88d2ab45039f6fa7e1ff7419d9cf0, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: d06bf48600f377466df0f56f066d525ee3f0a70995c5827551086d514784badc
- TakerPaymentSent · TakerPaymentReceived: 8cc5c24d6edb5d87086e27ac422a3a05e9d866b04590017c6f8523bc82bcb919
- TakerPaymentSpent: 1c7af30a197e14b15d6e67deb6ac49a8fc18f0daa933504d8178c003f1e63990
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.