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 1771947996 for transaction to be confirmed 2 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 b6d86de9d9c3903884b3554287fd767d3f65ad87b8cf58bb9f4c7587ed4c9834. Checked 2026-09-22 12:42:04 UTC.
caa727cd094f2d5fbf80690497699232763c7fc35558b5a0bb6c694e9479245f
Both payments are on their chains and locked to the same secret hash 7fc3380c6bd94932b2f2074b359cde37b6cf9af7, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: caa727cd094f2d5fbf80690497699232763c7fc35558b5a0bb6c694e9479245f
- MakerPaymentSpent: b6d86de9d9c3903884b3554287fd767d3f65ad87b8cf58bb9f4c7587ed4c9834
0476c5a76824c37eb594012b74c69f5b270e92d411b824e2a3ffe118efd29de7
Both payments are on their chains and locked to the same secret hash 7fc3380c6bd94932b2f2074b359cde37b6cf9af7, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 94bbf7c0eecf26ced6e1a9eb76d902e03ea455bd96ba39d17d12c6bf8fbcecf7
- TakerPaymentSent · TakerPaymentReceived: 0476c5a76824c37eb594012b74c69f5b270e92d411b824e2a3ffe118efd29de7
- TakerPaymentSpent: 8f36748a2cf3f2d24346979ee013ce8a2a7e60c3e1b1b323bed6cd83050868c9
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.