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 1790430895 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 37e63edc0ad7b94fddb849a96ef47442b3e99905e4abf59f4c0ead36273226e6. Checked 2026-09-27 01:58:06 UTC.
e8a2e851d7dac76d2121a48a41f116f0f2880cf7031573849f31eb1b8722a5ae
Both payments are on their chains and locked to the same secret hash c155a915416c83fcc8f5d51f6aa41c072fbb1a88, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: e8a2e851d7dac76d2121a48a41f116f0f2880cf7031573849f31eb1b8722a5ae
32fa80ebf422d799ae488c54d55748be110e7bcf5c05210d8dec74bc4d0502e3
Both payments are on their chains and locked to the same secret hash c155a915416c83fcc8f5d51f6aa41c072fbb1a88, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: bb4ca0af7011e2bc84324e153bd9957878905fb59f0ab6a4c99d3124b6385f6b
- TakerPaymentReceived: 32fa80ebf422d799ae488c54d55748be110e7bcf5c05210d8dec74bc4d0502e3
- TakerPaymentSpent: 9e68e4ae7b0d7282b604d57ae2b224cc25f3fbe4b5ca92f8d7c8f5ceee3cd6b0
Reported by kdf-statsdb.