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 1788660661 for transaction to be confirmed 1 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 3808cd693af2c15343d742d24a47a300d96174c0caa2320a47ef110a8043b683. Checked 2026-09-22 12:35:45 UTC.
52e4684fefdc764a72e501c17facac0dce67538335aeebfcaa80bb9354ee4fda
Both payments are on their chains and locked to the same secret hash 4d4616fd8fc8bae8e18a572c7ca948bf83304d36, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 52e4684fefdc764a72e501c17facac0dce67538335aeebfcaa80bb9354ee4fda
- MakerPaymentSpent: 3808cd693af2c15343d742d24a47a300d96174c0caa2320a47ef110a8043b683
6c68f4f723e8574727bbca5f4252ad9532febbc3dd769602822ccfd8f5f9ef0c
Both payments are on their chains and locked to the same secret hash 4d4616fd8fc8bae8e18a572c7ca948bf83304d36, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 6eed9dea6649d5254523e27b4c9235bd210d0b920e8ec8b05bd1fca0fc0b818f
- TakerPaymentSent · TakerPaymentReceived: 6c68f4f723e8574727bbca5f4252ad9532febbc3dd769602822ccfd8f5f9ef0c
- TakerPaymentSpent: a7748baf7ead9f02ce11e56cdca80e4c376254bdce14fbc5d475d122f3091d5a
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.