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 MakerPaymentWaitConfirmFailed.
taker_swap:1399] !wait for maker payment confirmations: rpc_clients:158] Waited too long until 1729462064 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.
533272e8d7b10b0c633376300319093fd14315ca01c8c59bdd094136bc5e18f7
Both payments are on their chains and locked to the same secret hash 80999215633366f652ca9aa87f7942b5d7b02470, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 533272e8d7b10b0c633376300319093fd14315ca01c8c59bdd094136bc5e18f7
cee4dd76a6cc3a558cab7c33fc607e7fcdf2dafb2c4987f5ad656ebeabe767bf
Both payments are on their chains and locked to the same secret hash 80999215633366f652ca9aa87f7942b5d7b02470, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: 6e27fd0c0dd3a2a97ff236fd747c841f365053f1722be7c1e1d1c406aad76e78
- TakerPaymentReceived: cee4dd76a6cc3a558cab7c33fc607e7fcdf2dafb2c4987f5ad656ebeabe767bf
- TakerPaymentSpent: 39a106320342e74808ad43d0751e0477ea34fedf11cad09136d236d93ad014dd
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.