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 1794339047 for transaction to be confirmed 7 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 e075fd94a34de315ed341419671e6f3b60bc9f50660c0fcabdec089d4f4cf442. Checked 2026-11-11 01:47:35 UTC.
31db0f072e2fb83d07284473f272f91a25d75922d791c09c15dff8cc7f88f1e4
Both payments are on their chains and locked to the same secret hash c159eab9355abebbc74ffb371fafaddea8021c57, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 31db0f072e2fb83d07284473f272f91a25d75922d791c09c15dff8cc7f88f1e4
b3b955aea8a178679fe289a2ceb055f8bb48438fd590b81ee371666b47229984
Both payments are on their chains and locked to the same secret hash c159eab9355abebbc74ffb371fafaddea8021c57, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: e4e0754d4b299c0f24bc2ff549268c84ab087577272513b46f1bba6b73b7fb1f
- TakerPaymentReceived: b3b955aea8a178679fe289a2ceb055f8bb48438fd590b81ee371666b47229984
- TakerPaymentSpent: 7799e27100e1eca2c491bd230d71c47d87f010d929338b2ad47f80c9d6f90eeb
Reported by kdf-statsdb.