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 1793398247 for transaction to be confirmed 7 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 6337324faeb03b4190b5bd051d9a2a4cbff9398f2090e439672fb69a044a3084. Checked 2026-10-30 22:51:51 UTC.
1adae46f50aa39efe7874123c8174af23750efd9ce3039114f731d6791c74965
Both payments are on their chains and locked to the same secret hash ac8d8e8ff4b415e2de1f516d3b6130fa405c033d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 1adae46f50aa39efe7874123c8174af23750efd9ce3039114f731d6791c74965
98c0639e7cb3efe9908c2918e3b6f87d69fa07ef8111bb4e00d4f6ccea15e1a3
Both payments are on their chains and locked to the same secret hash ac8d8e8ff4b415e2de1f516d3b6130fa405c033d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 328c7fd817587e91b97288f9cadcc1228fc4fb778c7101c5a30961331f6ce720
- TakerPaymentReceived: 98c0639e7cb3efe9908c2918e3b6f87d69fa07ef8111bb4e00d4f6ccea15e1a3
- TakerPaymentSpent: da113088c2616a05e9c485a710b5fa91ef65372a99889a3e5cb02338c587bd42
Reported by kdf-statsdb.