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 1780865474 for transaction to be confirmed 5 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 8fb09c65c067dfcdfd45f9329556738ac672300ca6d92dfe8c2b67d3f2cea2fa. Checked 2026-09-24 01:56:37 UTC.
d58ced3066c2ded0135c1ba2e911560e9d7eb0807f9244d189f28471a399c31c
Both payments are on their chains and locked to the same secret hash c6bfc05951e87db0ddedebe4b6d2641824dff08d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: d58ced3066c2ded0135c1ba2e911560e9d7eb0807f9244d189f28471a399c31c
- MakerPaymentSpent: 8fb09c65c067dfcdfd45f9329556738ac672300ca6d92dfe8c2b67d3f2cea2fa
9358523c6c571e47d43f83ccd2fddf065d780740c6a6064964e7f9f925992688
Both payments are on their chains and locked to the same secret hash c6bfc05951e87db0ddedebe4b6d2641824dff08d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 764cf7e29fc32aa3df2823185ce09ee40566bd2fe630be39082a927f11b2ff09
- TakerPaymentSent · TakerPaymentReceived: 9358523c6c571e47d43f83ccd2fddf065d780740c6a6064964e7f9f925992688
- TakerPaymentSpent: a6af93c5c78ed70429fd08042b27054ade9dbf5ff1c6f52e3e95e5d648c73394
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.