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 1790729626 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 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 abae98f339ed523c0fff57f547a61139a53c8d28f1ed48f61639fb9f4fe96a84. Checked 2026-09-30 08:09:29 UTC.
65e8c009361c0e1366a53bffc8e55cb3376a9dc356a103712e54e847ef9acfcf
Both payments are on their chains and locked to the same secret hash 8e30d251466ca4f1d4c8cd5a62c1b8ee6df38902, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 65e8c009361c0e1366a53bffc8e55cb3376a9dc356a103712e54e847ef9acfcf
548c871df26dea4ff84606b1e555c758e936f3478dd441761e077fc1e6b05bca
Both payments are on their chains and locked to the same secret hash 8e30d251466ca4f1d4c8cd5a62c1b8ee6df38902, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 80f806d8f4fe8aaa623580fc12e7e818dbb4db10595cd706f2d5b6886112dca3
- TakerPaymentReceived: 548c871df26dea4ff84606b1e555c758e936f3478dd441761e077fc1e6b05bca
- TakerPaymentSpent: fdb0461f781b752bd47ae30bb1107a0b74f79361762025f330ac3ca3b9e31460
Reported by kdf-statsdb.