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 1786037106 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 9f55c0399f2c42628332152b0e5bbddb8533db3895bc46171d75c1fba28a79a6. Checked 2026-09-24 01:56:09 UTC.
73436d3d8544db3c83b6d36ab6d2af4644dc1e4d3362689ceef98099a8456514
Both payments are on their chains and locked to the same secret hash 18a71d8181ecd18081c9cd1c77bf13f966086d9c, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 73436d3d8544db3c83b6d36ab6d2af4644dc1e4d3362689ceef98099a8456514
- MakerPaymentSpent: 9f55c0399f2c42628332152b0e5bbddb8533db3895bc46171d75c1fba28a79a6
6790a35e16d79f525bfe34ce16770fec5ce25872a8843fa17067dc1c59b164c2
Both payments are on their chains and locked to the same secret hash 18a71d8181ecd18081c9cd1c77bf13f966086d9c, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 9e3594e05445d8f9b3142b595bbcdd171ed7a37af270b3fc0b7624328373a663
- TakerPaymentSent · TakerPaymentReceived: 6790a35e16d79f525bfe34ce16770fec5ce25872a8843fa17067dc1c59b164c2
- TakerPaymentSpent: 8f7cc4a2c2f08b38a43f3f16d80246aba3df9e67c7fb759a3e88c18050a9923b
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.