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:1872] !wait for maker payment spend confirmations: rpc_clients:112] Waited too long until 1762248002 for transaction to be confirmed 3 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 e4573a589f4993ba935d762059b7c19f06aee15b409cb241b173bc2267f5b829. Checked 2026-09-22 12:51:50 UTC.
1d3a437fc9569eef23527dfc70cad4f591191ef5533b7ef47a34d25d8e88ec27
Both payments are on their chains and locked to the same secret hash 6e118f268fdaf323dd2eaae6749e3d9d89c265c0, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 1d3a437fc9569eef23527dfc70cad4f591191ef5533b7ef47a34d25d8e88ec27
- MakerPaymentSpent: e4573a589f4993ba935d762059b7c19f06aee15b409cb241b173bc2267f5b829
0573a707357dd4b8cd64310d82e120ed4a5854013f2ba80a7846618023f09b59
Both payments are on their chains and locked to the same secret hash 6e118f268fdaf323dd2eaae6749e3d9d89c265c0, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: c13c98d3febfb31edcc8fbffde379df41c2d5e2294caab70879792853073ca50
- TakerPaymentSent · TakerPaymentReceived: 0573a707357dd4b8cd64310d82e120ed4a5854013f2ba80a7846618023f09b59
- TakerPaymentSpent: 036507ddd241f0c46bd90bee049b2a68c131d5b1ecbe1760b900538bb8851b20
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.