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 1784070075 for transaction to be confirmed 5 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 7b57c96d559d5ef0052613e16b534974761bb31f39053bc996871954c8e621a1. Checked 2026-09-24 01:56:19 UTC.
140634b07c161f10fb51fa424e95eb0ac76f3eb329e2df2cef7aa60ceb56574d
Both payments are on their chains and locked to the same secret hash 3b6c279a34801423348be5920e3a7d3b9b0cf484, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 140634b07c161f10fb51fa424e95eb0ac76f3eb329e2df2cef7aa60ceb56574d
- MakerPaymentSpent: 7b57c96d559d5ef0052613e16b534974761bb31f39053bc996871954c8e621a1
22261ce523ba64d38e6d6ccd8843b815de518a327c3b55ad692544cd3a47bb0c
Both payments are on their chains and locked to the same secret hash 3b6c279a34801423348be5920e3a7d3b9b0cf484, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 3b888d14c38a7b9cfc1fc2600ff1ce54f8e01d1325bbf51643a98a676d146b3f
- TakerPaymentSent · TakerPaymentReceived: 22261ce523ba64d38e6d6ccd8843b815de518a327c3b55ad692544cd3a47bb0c
- TakerPaymentSpent: 2d5bce88794e9bd665db71546cde9f10fec016fad94fb7f45cdb3ed2406c8f9b
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.