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:2050] !wait for maker payment spend confirmations: rpc_clients:119] Waited too long until 1780887968 for transaction to be confirmed 1 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 b50ea4533a1c68e5a7bde7eba86ef2fa0731945f3bd888da013a983955d2e0af. Checked 2026-09-22 12:39:39 UTC.
fd4800572c6cc910a47a96399bb4bb23ad2f4547a9c6e4667682be85b0088115
Both payments are on their chains and locked to the same secret hash 52f8a2fae1edb851aa8ae49dfd1ee59a582d8600, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: fd4800572c6cc910a47a96399bb4bb23ad2f4547a9c6e4667682be85b0088115
- MakerPaymentSpent: b50ea4533a1c68e5a7bde7eba86ef2fa0731945f3bd888da013a983955d2e0af
d9924411a6c642c21631eb9e9d2959bdb79b28adf18d6935e44e19e16be3d667
Both payments are on their chains and locked to the same secret hash 52f8a2fae1edb851aa8ae49dfd1ee59a582d8600, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: c5d6b3b5fff504e23fa9d7ee7085f77a58a6d1f8143855a32ff4c378258f81ec
- TakerPaymentSent · TakerPaymentReceived: d9924411a6c642c21631eb9e9d2959bdb79b28adf18d6935e44e19e16be3d667
- TakerPaymentSpent: 9d6a7add1c96e64ba861d2076f4833f5586db5ace3ae386ec37748fb0131749f
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.