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 1792608876 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 65bc94435ec304ad2169715aee1e45cdb915a45bb10f4841624d318ccb8c834f. Checked 2026-10-22 05:19:30 UTC.
5ccf0d0324a1bba73726f6fc44eb458c14748ed350528446252131fab6566152
Both payments are on their chains and locked to the same secret hash ffb37eb61b804f3f45a70157f5950bfbd893b457, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 5ccf0d0324a1bba73726f6fc44eb458c14748ed350528446252131fab6566152
6e08c0199ea92d66e1fc416585ba6e92d54267d4222da3575aa9f7da4427571b
Both payments are on their chains and locked to the same secret hash ffb37eb61b804f3f45a70157f5950bfbd893b457, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: a3643fb11390f876bff0fe974e2926016e550b8809467751e98f988cdb0c72c2
- TakerPaymentReceived: 6e08c0199ea92d66e1fc416585ba6e92d54267d4222da3575aa9f7da4427571b
- TakerPaymentSpent: d8fa56dfea9fbb93327130e6a2be52884a6847d522099b77752a81a091cb570e
Reported by kdf-statsdb.