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 1793353716 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 630c25d35c9dfd856e97d8f0bdb6b9d54c527f880744e516d15671ed5f86e9c3. Checked 2026-10-30 10:31:43 UTC.
5a451d4060c821836613ef9e4e424f4eb58136714095d518a6bcdef37a1f6c3f
Both payments are on their chains and locked to the same secret hash 7123d47cc6323560a000209a379506b2e57a1d1f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 5a451d4060c821836613ef9e4e424f4eb58136714095d518a6bcdef37a1f6c3f
3c039073d0f0a2c768d9424f244b45065854cf0530b97f1544e14480e286c08c
Both payments are on their chains and locked to the same secret hash 7123d47cc6323560a000209a379506b2e57a1d1f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 1f7439dc6fca72153e654cc539ed5eaa1a366a6bcae073db9f048212d8b55f57
- TakerPaymentReceived: 3c039073d0f0a2c768d9424f244b45065854cf0530b97f1544e14480e286c08c
- TakerPaymentSpent: 1704afbd6152b392c7d82a9f85b2ee5372b65356182de00ac8f91382eeddbf89
Reported by kdf-statsdb.