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 1781067719 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 ea9ed8b6c67f441de6e068bf005dbff15449982cc9d6dacd8a1ff0ad01d77cb0. Checked 2026-09-24 01:56:33 UTC.
dffdc928d76d54b3946a9a49dcdb503d5dd9e2ba69132443d24b156ff8a832b5
Both payments are on their chains and locked to the same secret hash 61bc1ddc24c07925d6fff5168ee89c2884cdb108, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: dffdc928d76d54b3946a9a49dcdb503d5dd9e2ba69132443d24b156ff8a832b5
- MakerPaymentSpent: ea9ed8b6c67f441de6e068bf005dbff15449982cc9d6dacd8a1ff0ad01d77cb0
0e69de1f1d61f58917352aa12540179e2a3c2f0b12828beb337a86bbf9ca03b0
Both payments are on their chains and locked to the same secret hash 61bc1ddc24c07925d6fff5168ee89c2884cdb108, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: ddfca052b5bae4f15bf0afb0c38fcccf94c4b18ec86a8a4d7741b32883a6a039
- TakerPaymentReceived · TakerPaymentSent: 0e69de1f1d61f58917352aa12540179e2a3c2f0b12828beb337a86bbf9ca03b0
- TakerPaymentSpent: cebdc210dd31478595305695a2a1f5c6e061b630530eec98f68bf157034909c6
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.