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 1778041578 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 a28bb17de62f5e023ea3de75a44758a9e0c4b9678a70c101b162ee387158b398. Checked 2026-09-24 02:06:09 UTC.
5ea94ef9212de0eba43544805c14caca8217ffa8ab81f55a19138f38a7235f98
Both payments are on their chains and locked to the same secret hash fc980279320a2488ae0292013d61029bda72d28f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 5ea94ef9212de0eba43544805c14caca8217ffa8ab81f55a19138f38a7235f98
- MakerPaymentSpent: a28bb17de62f5e023ea3de75a44758a9e0c4b9678a70c101b162ee387158b398
f466fa420104923dd8d8461c55439f67193db242aaaa2a4fc584d163857b6662
Both payments are on their chains and locked to the same secret hash fc980279320a2488ae0292013d61029bda72d28f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: 195bd56276bd5b20e2b876ff4cc59662a4660880d9942c229406e198b5131a8b
- TakerPaymentSent · TakerPaymentReceived: f466fa420104923dd8d8461c55439f67193db242aaaa2a4fc584d163857b6662
- TakerPaymentSpent: 2143bf3922f671beab12022a69ed607d8adcbba9f6df5696ba9798a869fbfeeb
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.