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 1790932247 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 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 03e84d1d918e7b0969860eb8199da9fa93efd9a54778ab1b306bac9d0ad7fa49. Checked 2026-10-03 02:10:22 UTC.
35243c3afcc3e62e02ede6858dcc6bf1da23a612482e334e50c96b52aa39f3aa
Both payments are on their chains and locked to the same secret hash 86d60b1c6c2c0359682c3aba0f1ea0967562ef9c, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 35243c3afcc3e62e02ede6858dcc6bf1da23a612482e334e50c96b52aa39f3aa
f7ed3e78987f401b6c579eba900f19b3581ec120160e1da80010b70d6fa72433
Both payments are on their chains and locked to the same secret hash 86d60b1c6c2c0359682c3aba0f1ea0967562ef9c, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 4fe25ef749e6ba980699bb80431f2badde0ca5f00ac5fbe9a92e7fd0949001cd
- TakerPaymentReceived: f7ed3e78987f401b6c579eba900f19b3581ec120160e1da80010b70d6fa72433
- TakerPaymentSpent: 9871fbc8d536ba953592d28e18071ed32f4490f475b26ac2377c0a718140d23e
Reported by kdf-statsdb.