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 1759985011 for transaction to be confirmed 7 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 ea9d3617fe8fc77eb3fca48b26e3242297737a509a65d1c91cb5a3e1f0e9801a. Checked 2026-09-22 12:53:14 UTC.
ea4c0e9880388ca0ffdbbbf6909f5f50be0e314827ddcac25ab98d73548555e3
Both payments are on their chains and locked to the same secret hash 49d1c1dddef3cba406170ac0caaa539a3856083b, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: ea4c0e9880388ca0ffdbbbf6909f5f50be0e314827ddcac25ab98d73548555e3
- MakerPaymentSpent: ea9d3617fe8fc77eb3fca48b26e3242297737a509a65d1c91cb5a3e1f0e9801a
7f65a731b625def86c97a15293fd82c3ad9a04f07295be738b22c48c081f416b
Both payments are on their chains and locked to the same secret hash 49d1c1dddef3cba406170ac0caaa539a3856083b, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 8047e38447f42c00a1ea6354464f28fc3f9256f57e5e50efaedf116f0d7dfc9c
- TakerPaymentSent · TakerPaymentReceived: 7f65a731b625def86c97a15293fd82c3ad9a04f07295be738b22c48c081f416b
- TakerPaymentSpent: 15ecbcff1c9b96cdfecba7880a7da47128f230dfc8db891cf8723718aaed303b
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.