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 1786292660 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 d06bb97385c740885df634caad01c6fcae488d0dd442d53c67bbb3fd9d2a7329. Checked 2026-09-22 12:36:33 UTC.
fa19e1eeaed80397f66d81cd73ba492db9a94c2b5a7cb51a275c813fc423e134
Both payments are on their chains and locked to the same secret hash 76999cff582d8867c9653b76882faeea16016c25, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: fa19e1eeaed80397f66d81cd73ba492db9a94c2b5a7cb51a275c813fc423e134
- MakerPaymentSpent: d06bb97385c740885df634caad01c6fcae488d0dd442d53c67bbb3fd9d2a7329
3a890edc9fd5c8edefcae6d52e43187a9c3384b74e34ef7d46b11235283159fd
Both payments are on their chains and locked to the same secret hash 76999cff582d8867c9653b76882faeea16016c25, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: b211d0c1fc229170489d007710f06ae853b0c11c4ad0bd61c195bb4476ddf8e8
- TakerPaymentSent · TakerPaymentReceived: 3a890edc9fd5c8edefcae6d52e43187a9c3384b74e34ef7d46b11235283159fd
- TakerPaymentSpent: 0ddfa645c873c616753057ddca302f91ba9fb48f21dabd60d843d4b54e62e9ab
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.