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 1793917625 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 af1b0f29debbc1d621b0940495c4719ebc41f3c527a2f0798beba42b5b4bf811. Checked 2026-11-06 05:34:44 UTC.
9e0e7d025947e85d62041d90cc86b871cc5ab95a4f64432fa57aa70de957cc06
Both payments are on their chains and locked to the same secret hash e1895806fb2e110394db4afdc2d6cb005837c977, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: 9e0e7d025947e85d62041d90cc86b871cc5ab95a4f64432fa57aa70de957cc06
5b39283eb6e62c335ee32877b32f165716b56e466a7e0959a2f7d86819070d74
Both payments are on their chains and locked to the same secret hash e1895806fb2e110394db4afdc2d6cb005837c977, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: df4105d99a8870b87cc7efd99b47d894b3d031d065d83f87f045f6368ae4ae5a
- TakerPaymentReceived: 5b39283eb6e62c335ee32877b32f165716b56e466a7e0959a2f7d86819070d74
- TakerPaymentSpent: d4f57257767f67120da98d2009335253392b4d65c66c3ba4e29ec005a6cc7b21
Reported by kdf-statsdb-8762.