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 1788553588 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 c015ebaa0fae046413f5d17c6455545ceb71acbff019f4a40c83a7aefc5ec734. Checked 2026-09-22 12:35:52 UTC.
377493f27c2507ada3bbd8972555ebf2f2230364e704943d0667d510c32bc390
Both payments are on their chains and locked to the same secret hash 3fef59850229a89bb288cc6c06cd0091aeaba5a8, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 377493f27c2507ada3bbd8972555ebf2f2230364e704943d0667d510c32bc390
- MakerPaymentSpent: c015ebaa0fae046413f5d17c6455545ceb71acbff019f4a40c83a7aefc5ec734
d8f5691d61611a81de2b87df878734b6373213832c794cf0ded3bcba018c7ab7
Both payments are on their chains and locked to the same secret hash 3fef59850229a89bb288cc6c06cd0091aeaba5a8, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 135d17c222d78b2720b56a3cf0a89b78b6bda8c2e3290701ad4ceeca36c02fe9
- TakerPaymentReceived · TakerPaymentSent: d8f5691d61611a81de2b87df878734b6373213832c794cf0ded3bcba018c7ab7
- TakerPaymentSpent: 63cc3a570b65aef81a905d34b8623ca68019c3eaed7fdb5a75dd40a0ede135e2
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.