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:1701] !taker_coin.wait_for_confirmations: rpc_clients:170] Waited too long until 1724417437 for transaction to be confirmed 5 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.
752bda8fe06940827fac44775e061b3c1b0b928ad913c8fb74a33d50b45fc35d
Both payments are on their chains and locked to the same secret hash 3a03c9389d4209c1fa5b7536500c0b50a366bf2e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 752bda8fe06940827fac44775e061b3c1b0b928ad913c8fb74a33d50b45fc35d
4c45116fa01cdb422e8c6e1d8520e2750838f2b73395212f0205a90738f5afcc
Both payments are on their chains and locked to the same secret hash 3a03c9389d4209c1fa5b7536500c0b50a366bf2e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 66cd428c43d19db8fcebcc93ea2c9b9370314c4bf95c23d399c55ffa497d41b0
- TakerPaymentSent · TakerPaymentReceived: 4c45116fa01cdb422e8c6e1d8520e2750838f2b73395212f0205a90738f5afcc
- TakerPaymentSpent: 0e84dc2d55f3877e9fc8bd7f037fe25decd73773896a5ad19f98ed27f6fe20bd
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.