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:1904] !wait for maker payment spend confirmations: rpc_clients:112] Waited too long until 1761531375 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 5c0c6ccd0f3ad76afcaa8fac75505d86ac5af536e7862ed9454794fb2dd4ad60. Checked 2026-09-22 12:52:22 UTC.
51656b573cf391e76b1b119587a4fdc6b544ddfc36f25fea19a50111a6884cfa
Both payments are on their chains and locked to the same secret hash bce3ab6e970d6ba98a8e315a5671bb5b315a43e2, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 51656b573cf391e76b1b119587a4fdc6b544ddfc36f25fea19a50111a6884cfa
- MakerPaymentSpent: 5c0c6ccd0f3ad76afcaa8fac75505d86ac5af536e7862ed9454794fb2dd4ad60
1d2106ad5b6c7b0554b1762e842a6c459fbcea8f74f99e144b8390148762e507
Both payments are on their chains and locked to the same secret hash bce3ab6e970d6ba98a8e315a5671bb5b315a43e2, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: d3f8f35b6137951fd62e02af9cdd88a69c4bf24422e64666d077a1f94843f352
- TakerPaymentReceived · TakerPaymentSent: 1d2106ad5b6c7b0554b1762e842a6c459fbcea8f74f99e144b8390148762e507
- TakerPaymentSpent: e33b69e2e9858bcb973ec1bfcdc277d4ff1ba7705fc807227fbc8502c1f6fe12
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 defistats-gleec.