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:1959] !wait for maker payment spend confirmations: rpc_clients:112] Waited too long until 1760935345 for transaction to be confirmed 2 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 12eca8b2fb48bd66d0eb919fb43d1df649c7337eae8e576037a762c94dd193a0. Checked 2026-09-22 12:52:30 UTC.
06863a2d8008906f115b949e18a6ea98e0f3247cad71cfd5151029c1070b7c05
Both payments are on their chains and locked to the same secret hash cc4f39e9b180820f4bc37203239da8935d9bf692, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 06863a2d8008906f115b949e18a6ea98e0f3247cad71cfd5151029c1070b7c05
- MakerPaymentSpent: 12eca8b2fb48bd66d0eb919fb43d1df649c7337eae8e576037a762c94dd193a0
eed89a16ee24e940ca96ed7ace2bd39b5c7fdb19b7c811a81564f94cce3493c4
Both payments are on their chains and locked to the same secret hash cc4f39e9b180820f4bc37203239da8935d9bf692, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: f80d1d832e446a7e0a4a1df957d0aa2b596514b6e58b026f977f9cab004abc09
- TakerPaymentSent · TakerPaymentReceived: eed89a16ee24e940ca96ed7ace2bd39b5c7fdb19b7c811a81564f94cce3493c4
- TakerPaymentSpent: 4144db22ca5d6cff51a97e77ed384f0ad70a39487951ef38d50858ca11e5226c
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.