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 1764810209 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 863aa9270226e82ace2ded91e6394e8b81fc7b60799a58e3feed16dd1517ada8. Checked 2026-09-22 12:48:46 UTC.
9b98f5d6b0c6351e16028df053f4f57a844e54d6066e2e1b14f241ffca2a253d
Both payments are on their chains and locked to the same secret hash a972f65c0de60d785425a95c9e14f985222384bb, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 9b98f5d6b0c6351e16028df053f4f57a844e54d6066e2e1b14f241ffca2a253d
- MakerPaymentSpent: 863aa9270226e82ace2ded91e6394e8b81fc7b60799a58e3feed16dd1517ada8
8c7acb352ca18709b20e2d2dd709f8e31d06085ebce08d32c5d57896db6a60ce
Both payments are on their chains and locked to the same secret hash a972f65c0de60d785425a95c9e14f985222384bb, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: 1505398e5f5460439be440f1a6ed1d17b0ee28acfef598c4aec4ec4d2f091d43
- TakerPaymentReceived · TakerPaymentSent: 8c7acb352ca18709b20e2d2dd709f8e31d06085ebce08d32c5d57896db6a60ce
- TakerPaymentSpent: e3866821fe41c507988604fdb578192ed8b53527c3082d3c7411cd4e3ad909c1
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.