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:2046] !wait for maker payment spend confirmations: rpc_clients:119] Waited too long until 1763661076 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 89cc99023c22de59eb1c9afae44e26118c6a25dc888d47998adcb6db1d9b8d6e. Checked 2026-09-22 12:50:42 UTC.
c5be7bac718f6588be1f6409b6e2584d65c6b8b2b78165e7e986982950c6bd19
Both payments are on their chains and locked to the same secret hash 024951fc52ebcdb68951341d3d0fdd6f03cf4334, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: c5be7bac718f6588be1f6409b6e2584d65c6b8b2b78165e7e986982950c6bd19
- MakerPaymentSpent: 89cc99023c22de59eb1c9afae44e26118c6a25dc888d47998adcb6db1d9b8d6e
7cff0687df4219c4a36cb65f43f94c0fa29d1f006c59122963ef30b233fa8981
Both payments are on their chains and locked to the same secret hash 024951fc52ebcdb68951341d3d0fdd6f03cf4334, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: ebf8f25776f86b26d261adbf19470fff65f80a828b0c552f239d33d0b3fb9e88
- TakerPaymentSent · TakerPaymentReceived: 7cff0687df4219c4a36cb65f43f94c0fa29d1f006c59122963ef30b233fa8981
- TakerPaymentSpent: 3b37bb8ba9c195464fbe48b11ba61ae6316ada6f8e94e8f7c3ff8fd83b00f217
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.