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 1789760784 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 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 dac1947b6ea85b11c6972790f43dd9717850d4e0cd0fadfb7fa6b7b27271c77f. Checked 2026-09-22 12:35:29 UTC.
adbdb1cc1e141a53fbf894fe0de6903669130a1b57c4ccbfc3bddb7983465774
Both payments are on their chains and locked to the same secret hash 8012ae2faf2e365091cfbbad3b62aa44bca8da39, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · adbdb1cc1e141a53fbf894fe0de6903669130a1b57c4ccbfc3bddb7983465774
b4765846f59493543ad545fac6d59f4a7af2c297944c80c338a641374ba9fe89
Both payments are on their chains and locked to the same secret hash 8012ae2faf2e365091cfbbad3b62aa44bca8da39, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · d4c694396bda19552cab5faa892579548a1b01cf3a5a53b07113e8b1911e777d
- TakerPaymentReceived · b4765846f59493543ad545fac6d59f4a7af2c297944c80c338a641374ba9fe89
- TakerPaymentSpent · a0589e1e444dccbf1799a8db7a246409bf700e7ed758d60a1832b6be8abb2ed0
Reported by defistats-gleec.