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:2044] !wait for maker payment spend confirmations: rpc_clients:119] Waited too long until 1763358558 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 63ab031c35eca1741836f075a736e9071b9a690db198c91a69b20276a0301550. Checked 2026-09-22 12:50:54 UTC.
2f425878aedf7ef87ccdeca00dc93017ced132f3120a3151d5d3f4a9b97490aa
Both payments are on their chains and locked to the same secret hash 51f560757174008095c9cacdb38205f4f8522fec, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 2f425878aedf7ef87ccdeca00dc93017ced132f3120a3151d5d3f4a9b97490aa
- MakerPaymentSpent: 63ab031c35eca1741836f075a736e9071b9a690db198c91a69b20276a0301550
dd1675e950d2555fe47c4003ba2ef10112f66587d445b1727f154b69e4976e9b
Both payments are on their chains and locked to the same secret hash 51f560757174008095c9cacdb38205f4f8522fec, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: f5a0a1c2943b903b2f6e7c2f273e4bbaefde62c6485de828a71ef53a06bb87a4
- TakerPaymentSent · TakerPaymentReceived: dd1675e950d2555fe47c4003ba2ef10112f66587d445b1727f154b69e4976e9b
- TakerPaymentSpent: 49fcd5ce478efa8f7621fb1eb16b54aff3a5f2c9f52aabaab778740a5b7bd4df
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 defistats-gleec.