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 1758765218 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 7785671052897a8dd340b4df1104ddb636dfd5ad5e78a7c1dbfac530896f6752. Checked 2026-09-22 12:53:50 UTC.
913c74ba20a99fce05c489b8bdbc2cb3ded7e0719275fd1590b00149edab3b69
Both payments are on their chains and locked to the same secret hash a799d94dd8b57cc5ca236daf761f7f6a37011db6, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 913c74ba20a99fce05c489b8bdbc2cb3ded7e0719275fd1590b00149edab3b69
- MakerPaymentSpent: 7785671052897a8dd340b4df1104ddb636dfd5ad5e78a7c1dbfac530896f6752
13c85a6cb327e177b6e2755a4ef6a62e23786c7678fea49d5be1ca851406c4d9
Both payments are on their chains and locked to the same secret hash a799d94dd8b57cc5ca236daf761f7f6a37011db6, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: aeb7d7cff2070ca135caa024943b569297169b0f359486df9bf5ef2f57615f96
- TakerPaymentSent · TakerPaymentReceived: 13c85a6cb327e177b6e2755a4ef6a62e23786c7678fea49d5be1ca851406c4d9
- TakerPaymentSpent: ef8297a4bba8e5faefa39855977f17bdb4e459dee58a4d031c4f448fac95c775
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.