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:1909] !wait for maker payment spend confirmations: rpc_clients:112] Waited too long until 1774633931 for transaction to be confirmed 4 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 b72f3c6a5931862336bb67ae9bbdf1248f3de9b00a376783e73de5865459a71d. Checked 2026-09-22 12:40:46 UTC.
959601e34ac4f26dde27c16357a2e2f984566de5878d9868a1338f392df3229b
Both payments are on their chains and locked to the same secret hash 4a819863a8659bf51833361b041a69fe40347758, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 959601e34ac4f26dde27c16357a2e2f984566de5878d9868a1338f392df3229b
- MakerPaymentSpent: b72f3c6a5931862336bb67ae9bbdf1248f3de9b00a376783e73de5865459a71d
a422fc260bb26ef90201561bb30cc5730db69f96a1ad0ba1d6dbfc6072ce87c9
Both payments are on their chains and locked to the same secret hash 4a819863a8659bf51833361b041a69fe40347758, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 553a1bf1d1ff10b22ade65c50165bcdb3c3df91819e0129f66ac0314e0c1f4f4
- TakerPaymentSent · TakerPaymentReceived: a422fc260bb26ef90201561bb30cc5730db69f96a1ad0ba1d6dbfc6072ce87c9
- TakerPaymentSpent: dc4296bf84356aeb24fbe604ce36d85e7567815e6845a3d07b054ca0c5d5f230
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.