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 1778967819 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 3d79f5e5a74ec38d07cc13a0540e446015480635f78e753fb74a438bfbabf196. Checked 2026-09-22 12:39:57 UTC.
5f6906d83460a56a9bfe33a61d4b658ba509e5d8c3e91ad234c3ece3c6303d54
Both payments are on their chains and locked to the same secret hash ba10f87e2d552bd7211c40b921f910764580575c, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentReceived · MakerPaymentSent: 5f6906d83460a56a9bfe33a61d4b658ba509e5d8c3e91ad234c3ece3c6303d54
- MakerPaymentSpent: 3d79f5e5a74ec38d07cc13a0540e446015480635f78e753fb74a438bfbabf196
4ae2d1b7c8a9270af11eecf9d30944431de596bd9e8fb8ce59ec13c0a09b92f6
Both payments are on their chains and locked to the same secret hash ba10f87e2d552bd7211c40b921f910764580575c, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 89500d71b3cffba75748828c83e890382a85bd6a71d279b7404350679f67c962
- TakerPaymentSent · TakerPaymentReceived: 4ae2d1b7c8a9270af11eecf9d30944431de596bd9e8fb8ce59ec13c0a09b92f6
- TakerPaymentSpent: 3e9d4af2a2e4491586fb3f65f81953283564810b061cdb39f8c15eba0565e976
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.