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 1781560312 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 d40c1958dc61424feb489f98cf4beac40602df342448e74568493d7115906b4e. Checked 2026-09-24 01:56:28 UTC.
3487f07fd40eac71c3b21e83536828e56131fb5539019453861a7984bb31d8b8
Both payments are on their chains and locked to the same secret hash fa8993e4b4f5a8ab885cd1b43034c6505c39975d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 3487f07fd40eac71c3b21e83536828e56131fb5539019453861a7984bb31d8b8
- MakerPaymentSpent: d40c1958dc61424feb489f98cf4beac40602df342448e74568493d7115906b4e
4dc94f85f67ef803ace4aa0628e59a5fbd11d91152d976fbd682aecc688e1531
Both payments are on their chains and locked to the same secret hash fa8993e4b4f5a8ab885cd1b43034c6505c39975d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 06dc28b467dec33f8ce3075b900ef5d5e2727a92788c575ffdaeb9d5804e7056
- TakerPaymentSent · TakerPaymentReceived: 4dc94f85f67ef803ace4aa0628e59a5fbd11d91152d976fbd682aecc688e1531
- TakerPaymentSpent: dc11b40bf35f3d0c9b6ac628e80660145fa34aef73ee78168981e37261067630
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.