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:2050] !wait for maker payment spend confirmations: rpc_clients:119] Waited too long until 1766294216 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 b29dc654f3b3e07b28d2827bb41b13fe6575f647b756ac9caa441eb29af72512. Checked 2026-09-24 18:14:14 UTC.
2756cedb7cae4a230172c39942f8f50367ba0fb32c63494426b8e6a468a015db
Both payments are on their chains and locked to the same secret hash 2ef1c4127228a47c2561772690f34df858fdfcfc, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 2756cedb7cae4a230172c39942f8f50367ba0fb32c63494426b8e6a468a015db
- MakerPaymentSpent: b29dc654f3b3e07b28d2827bb41b13fe6575f647b756ac9caa441eb29af72512
e79e7c729c01e42b0513cad0179e0076e587a04d059209adc019d23293f4206a
Both payments are on their chains and locked to the same secret hash 2ef1c4127228a47c2561772690f34df858fdfcfc, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 59b82b9a3b9bbeb6be8401125a8b9fce902e0c820492fc191d77375cb2dd64ce
- TakerPaymentSent · TakerPaymentReceived: e79e7c729c01e42b0513cad0179e0076e587a04d059209adc019d23293f4206a
- TakerPaymentSpent: 42eae327d6bf6cde30c596364903d0a50986b5f09a8121eaa9d50f932590018c
No flags are stored against this swap. Flags are written while a swap sits inside a live pricing window, so on an older swap their absence means it was never assessed rather than that it was assessed and found clean.
Reported by kdf-statsdb-8762.