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 1784652029 for transaction to be confirmed 3 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 9c0066720461d4b854fa3176ae223264465744e0142e40664dc96baccd724354. Checked 2026-09-24 01:56:15 UTC.
2893a8597c792bf9443072890f9b03db82fb2fab930ad876c4ba21c25342d3e1
Both payments are on their chains and locked to the same secret hash e70bfa09f432c52bccbfaade3504cc3eab4585da, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 2893a8597c792bf9443072890f9b03db82fb2fab930ad876c4ba21c25342d3e1
- MakerPaymentSpent: 9c0066720461d4b854fa3176ae223264465744e0142e40664dc96baccd724354
3a78013e39419709e3143ce29ff012339e48750f60bf4b74ef7b67ee4e4cc1ea
Both payments are on their chains and locked to the same secret hash e70bfa09f432c52bccbfaade3504cc3eab4585da, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 04cda9a340d839d498343a994ef6c5772e784972d11b73f3ba2fe7b79d832c37
- TakerPaymentReceived · TakerPaymentSent: 3a78013e39419709e3143ce29ff012339e48750f60bf4b74ef7b67ee4e4cc1ea
- TakerPaymentSpent: f0200804823888c29ac296633987cc90846782a6605e1ae3823c7b7b5abee89e
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.