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 1788553631 for transaction to be confirmed 1 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 f353404ae2f730a1ce8012b5e1377ddde88d661e673f491348ea9a194782d28b. Checked 2026-09-22 12:35:50 UTC.
02e4cab535aa1e991cc3702fec2004d902e636e472ce80aca78ca6f269188d0d
Both payments are on their chains and locked to the same secret hash 311e5446e63555ff5f883f9efec4459bf6f76bdb, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 02e4cab535aa1e991cc3702fec2004d902e636e472ce80aca78ca6f269188d0d
- MakerPaymentSpent: f353404ae2f730a1ce8012b5e1377ddde88d661e673f491348ea9a194782d28b
9e98b7634e29531e42594b823229c6ca954a13b798e6ff5feb83ba96ad1140bf
Both payments are on their chains and locked to the same secret hash 311e5446e63555ff5f883f9efec4459bf6f76bdb, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 95250e7b09ad28ffec72ccb4a37899cb55bd677ddc7f39a7df808671f10bbd9f
- TakerPaymentSent · TakerPaymentReceived: 9e98b7634e29531e42594b823229c6ca954a13b798e6ff5feb83ba96ad1140bf
- TakerPaymentSpent: 27b04343a58a1a6342f336f37b8b2078f2b80f8fbb119e79d1522ca1a4d282d6
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.