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 1783245368 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 4537caaf27c1c5496a5adf37148c8aab85e80829469b5b140ef32c91f4155052. Checked 2026-09-22 12:38:41 UTC.
6d7fdae211d45788fd06341b952021bc68b6b2db3fcd1325970e7cb4bde5a8fe
Both payments are on their chains and locked to the same secret hash c46ecfe97e1cd40be673a63fab13bec991a58533, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 6d7fdae211d45788fd06341b952021bc68b6b2db3fcd1325970e7cb4bde5a8fe
- MakerPaymentSpent: 4537caaf27c1c5496a5adf37148c8aab85e80829469b5b140ef32c91f4155052
03cef9da18d9014fbce235c59a1c02f11daae2b2fe0fe405dfddded2a61fe61c
Both payments are on their chains and locked to the same secret hash c46ecfe97e1cd40be673a63fab13bec991a58533, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: d50244fd6dffc346d9b243734b11a051039c71341a65e154344501076d4ea162
- TakerPaymentSent · TakerPaymentReceived: 03cef9da18d9014fbce235c59a1c02f11daae2b2fe0fe405dfddded2a61fe61c
- TakerPaymentSpent: 5a3f528e93c02d5853ef34c1004c53169ccd533cef99bfbe40dbe6cab0fbf58e
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.