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 1792942991 for transaction to be confirmed 5 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 0786a738ec990b06f89ed5ee9972d1f892acaf058f0afa4176e780c61f0587fc. Checked 2026-10-27 11:50:49 UTC.
94eb934c007eed7ebe8367887e4493927cba66f4894f99108d3b20e1f73b6bbf
Both payments are on their chains and locked to the same secret hash ef7a7e624c96257c5755476d1c92e64246b8b627, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 94eb934c007eed7ebe8367887e4493927cba66f4894f99108d3b20e1f73b6bbf
1f55f127233e17496418e9509760d4cda9ac3dcde2d4ff7ac05c1feb9ddf9462
Both payments are on their chains and locked to the same secret hash ef7a7e624c96257c5755476d1c92e64246b8b627, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 0e34f93cb9c399c03cbcca8c9972b955d531ba37c4fb06df7ea8564930929237
- TakerPaymentReceived: 1f55f127233e17496418e9509760d4cda9ac3dcde2d4ff7ac05c1feb9ddf9462
- TakerPaymentSpent: 73c46cd1b2e31ae38d5bda7b2633c8f0c66d3b75aeb2e39a9cf92222cb179bad
Reported by kdf-statsdb.