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 1777424512 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 f935044ab00b354313da978c775658cd0d28c6ecf1eda23311523e4d025bdd92. Checked 2026-09-22 12:40:15 UTC.
1b42c307b84553acff7cf691402efe15af7731458e811b5397c8fc7248b1c07f
Both payments are on their chains and locked to the same secret hash 149dc42fc4209cc4b04dcf48c911ed82173c8b2b, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 1b42c307b84553acff7cf691402efe15af7731458e811b5397c8fc7248b1c07f
- MakerPaymentSpent: f935044ab00b354313da978c775658cd0d28c6ecf1eda23311523e4d025bdd92
3d80375b67bc6191a128259c2b307e808663ca4c7120b9a20a39f08289d61935
Both payments are on their chains and locked to the same secret hash 149dc42fc4209cc4b04dcf48c911ed82173c8b2b, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: aa11eb872f49b07c6756f67aab1ba0a83b2363f86bd0c7424a9f5f435653220e
- TakerPaymentSent · TakerPaymentReceived: 3d80375b67bc6191a128259c2b307e808663ca4c7120b9a20a39f08289d61935
- TakerPaymentSpent: 3ba5319527c8c5412f07300f340ad9e8e4c52cdd8ce36e4d28716c5d2071919d
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.