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 1776789299 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 0afa81489263928a9eae648dc93b94fbcfa1d253ffaacee3e908490716755a96. Checked 2026-09-24 02:06:30 UTC.
03b0f935c5555b16260dfcb79f16a994f3c33a8e154c9a211b87d3f7fae05a59
Both payments are on their chains and locked to the same secret hash 648f9a3eb110e5dd8cc2a8f15fd18b1b1600945b, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 03b0f935c5555b16260dfcb79f16a994f3c33a8e154c9a211b87d3f7fae05a59
- MakerPaymentSpent: 0afa81489263928a9eae648dc93b94fbcfa1d253ffaacee3e908490716755a96
9bc9303a4cc9922179cbcdf1de8682fd73c6e2fd00252cd05d6baab46e2f1c3f
Both payments are on their chains and locked to the same secret hash 648f9a3eb110e5dd8cc2a8f15fd18b1b1600945b, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: 7bd7cafab1291b82ce2e9d44ffa3671e9bbe084391c55aa59517611ee7fb3141
- TakerPaymentReceived · TakerPaymentSent: 9bc9303a4cc9922179cbcdf1de8682fd73c6e2fd00252cd05d6baab46e2f1c3f
- TakerPaymentSpent: 794fd1d7985e3c75c1102d0dc7f5e4fd116755ea54d04a411d2d1d4f713f4fa9
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.