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 1781758087 for transaction to be confirmed 1 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 eaa7dd5058ee914b89364bc48f024c32a59d2a8393968404b07047da3305e2aa. Checked 2026-09-24 17:14:16 UTC.
d8bdcf69f6d5cf32f3367d3aef29aa9bd2d7816c7db6097c91b643fc555fa7ec
Both payments are on their chains and locked to the same secret hash 8131237e6b0f921869923e76d1af24ebcf774f50, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: d8bdcf69f6d5cf32f3367d3aef29aa9bd2d7816c7db6097c91b643fc555fa7ec
- MakerPaymentSpent: eaa7dd5058ee914b89364bc48f024c32a59d2a8393968404b07047da3305e2aa
451a371bed50263de556e7fe5cf2d99d0be78ba97235a860014936758840e090
Both payments are on their chains and locked to the same secret hash 8131237e6b0f921869923e76d1af24ebcf774f50, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 7635c065a96343d409924139b8b40dd4082b288c706e73c7ab6c11c3c60890f3
- TakerPaymentSent · TakerPaymentReceived: 451a371bed50263de556e7fe5cf2d99d0be78ba97235a860014936758840e090
- TakerPaymentSpent: e423794dc3da52c50a1f3640642e1b19c2a669cfb6de73627dd54821bfe7f9b6
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.