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 1769938293 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 be retried for as long as the payment is unspent, and until the timelock passes nobody else can touch 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 1adc0f060c0c172fce6d85b440029f22fce9763f3619716a4f1ee76df00d655a. Checked 2026-10-01 19:30:17 UTC.
56d655baf728dab220a74655731138b8b793eaa6911572e7db4797764b250656
ARRR settles as ZHTLC, whose transfers do not appear as an output any chain server can read, so the transaction the record names cannot be checked against a chain here
- MakerPaymentReceived: 56d655baf728dab220a74655731138b8b793eaa6911572e7db4797764b250656
- MakerPaymentSpent: 1adc0f060c0c172fce6d85b440029f22fce9763f3619716a4f1ee76df00d655a
5daaa5ec226ef0c97dc9d25dedf266124494f305b57e8dce444a1a0b9891d4b2
confirmed on-chain, calling the swap contract, locked to this swap's secret hash
- TakerFeeSent: fa15886b0f09952d2e1a9ba3ddf9f040706a3a9ac5b554ad4dbd688923c06b80
- TakerPaymentSent: 5daaa5ec226ef0c97dc9d25dedf266124494f305b57e8dce444a1a0b9891d4b2
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 kdf-statsdb-8762.