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 1782326988 for transaction to be confirmed 2 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 be retried for as long as the timelock holds, and whether it was 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 3134921282cd42601818770810552e0a05055965fc4629bb1807db62567036cb. Checked 2026-09-22 12:39:06 UTC.
166b0ea172e5de99821e88523ce33ade59b264439a897264e4322aee042c98cd
Both payments are on their chains and locked to the same secret hash ddc8ec1f618e4df9540597fc6e524d13513e8240, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 166b0ea172e5de99821e88523ce33ade59b264439a897264e4322aee042c98cd
7f6e667d9600d4641676f57feefb283581d8791f749eaab5a37f55720d06040f
Both payments are on their chains and locked to the same secret hash ddc8ec1f618e4df9540597fc6e524d13513e8240, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 7003e03932e82efc9b734b094ce03262c46ec5800fdbca910764bc71cf5ee2f0
- TakerPaymentReceived · 7f6e667d9600d4641676f57feefb283581d8791f749eaab5a37f55720d06040f
- TakerPaymentSpent · a0e14d416c68689cde3edfdf8a46cdf924f255f1867faf10c9837fbace5ee7b4
No anomalies were recorded against this swap.
Reported by defistats-gleec.