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 record stops at MakerPaymentSpendConfirmFailed. The taker's claim on the maker's coin was broadcast but not seen to confirm.
taker_swap:2052] !wait for maker payment spend confirmations: rpc_clients:119] Waited too long until 1788553531 for transaction to be confirmed 1 times
By this step both payments were on their chains and the price had been struck, so the trade counts toward the reference price. The claim can still be made for as long as the payment is unspent, and since the timelock has passed the payer can take it back as well, so whichever lands first settles it. Whether it was retried is a question for the chain rather than for this log.
The chain says the claim landed: the payment was spent with the preimage, in 556b7c7d94bf88552ac1076161c520f75f38210255aa9bea327849e2569e30f3. Checked 2026-09-22 12:35:55 UTC.
ddf0a82865c428175c2865cd1837128db732f903cc54a49c86bd0b14742c4286
Both payments are on their chains and locked to the same secret hash a1e8120c16b7e18362509ade02cf0ed9dd483158, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: ddf0a82865c428175c2865cd1837128db732f903cc54a49c86bd0b14742c4286
- MakerPaymentSpent: 556b7c7d94bf88552ac1076161c520f75f38210255aa9bea327849e2569e30f3
f77e2d932b5c5d36e2f55910987e561be9535e421e5b1b0d16c3f259f307eab4
Both payments are on their chains and locked to the same secret hash a1e8120c16b7e18362509ade02cf0ed9dd483158, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 74f10f523cf251e6cad647754e248dcdeeeae0d491c1c49879e4621bc74c5366
- TakerPaymentSent · TakerPaymentReceived: f77e2d932b5c5d36e2f55910987e561be9535e421e5b1b0d16c3f259f307eab4
- TakerPaymentSpent: b2ff6b45778f88bce650dde3ba71cfdc3bd15b612133c4bbec3e5748d2125443
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 defistats-gleec.