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:1959] !wait for maker payment spend confirmations: rpc_clients:112] Waited too long until 1759459805 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 895d884419df47096b8c4b8573453446020e4d325dc57b86e6d026c9e7a98fcb. Checked 2026-09-22 12:53:26 UTC.
1006b89f0ddad8337fb2ce7865f72b760f361620e7fb623b704081307ac7b84a
Both payments are on their chains and locked to the same secret hash f32715c88b81c13b07b0b9603623e975b87f9ae3, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 1006b89f0ddad8337fb2ce7865f72b760f361620e7fb623b704081307ac7b84a
- MakerPaymentSpent: 895d884419df47096b8c4b8573453446020e4d325dc57b86e6d026c9e7a98fcb
622c0b4304e573c3c3009b1251e8cbf70e1ba007e013d1069646f08664188a54
Both payments are on their chains and locked to the same secret hash f32715c88b81c13b07b0b9603623e975b87f9ae3, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 9e3524dc3a555c33295475c5d905d2a8749882dbbe35e0b9bb39113a09f5869d
- TakerPaymentSent · TakerPaymentReceived: 622c0b4304e573c3c3009b1251e8cbf70e1ba007e013d1069646f08664188a54
- TakerPaymentSpent: ee1ad664c4e04b46e54893ca91cfa318b45752901d5a665ae50ea9e4c81d7901
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.