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 MakerPaymentSpendFailed. The taker's claim on the maker's coin was rejected; it can be retried for as long as that payment is unspent.
taker_swap:2010] mm2src\coins\utxo\ "utxo_common:1025] utxo_common:977] client:1132] : failed to parse list of 11 headers (coin=RVN, from=4436140, requested_count=11): UnexpectedEnd"
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 46f2b3643cec94ca2244d61e2d526f646359ec30ea04ffd97bf20e263ec1c66a. Checked 2026-09-22 12:38:52 UTC.
b879d4e8542965feaea1bea709e1bc72fae68145a872b044887f9900b96640db
Both payments are on their chains and locked to the same secret hash 392436de9022b8525eb69f75602c5bb34f978b9d, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: b879d4e8542965feaea1bea709e1bc72fae68145a872b044887f9900b96640db
f3fe7c424f254dcfa0459e2078f4c6a95b6b59cc310db297217186954ebb0672
Both payments are on their chains and locked to the same secret hash 392436de9022b8525eb69f75602c5bb34f978b9d, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: c63c6671653edd027723d47d6f597e6cf4c81d0bbbe0159910b15bf165c42acf
- TakerPaymentSent · TakerPaymentReceived: f3fe7c424f254dcfa0459e2078f4c6a95b6b59cc310db297217186954ebb0672
- TakerPaymentSpent: c00ac8c6c62f54ad63695947d503607926d8459fe04253441d8a68a9635c6388
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.