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:2008] mm2src\coins\utxo\ "utxo_common:998] utxo_common:950] client:1132] : failed to parse list of 11 headers (coin=RVN, from=4482001, 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 223dfe1666d2a7a40cdb3c31c957e6a782f2830fa0c24432d0fd75fe8f138919. Checked 2026-09-22 12:36:48 UTC.
5044b79f4cd6a58d673fe9b2fa26e05da1813da5df48bbff19da408e546aa1fb
Both payments are on their chains and locked to the same secret hash 08782cfca43aff663be6909d9967f5cd1e170a5f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 5044b79f4cd6a58d673fe9b2fa26e05da1813da5df48bbff19da408e546aa1fb
31c5c7a6dcd146d5f8020d0cff473ba8d5c0a417faefbc62f37237e1341b151e
Both payments are on their chains and locked to the same secret hash 08782cfca43aff663be6909d9967f5cd1e170a5f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 8f540096c9ea7ff928d5c2290520a19cbfcb3dc27b425de4bd45c3542da89f49
- TakerPaymentSent · TakerPaymentReceived: 31c5c7a6dcd146d5f8020d0cff473ba8d5c0a417faefbc62f37237e1341b151e
- TakerPaymentSpent: 35059a882f6c24e09d513e3f0048fbb38e8e513fd333386dcd73e7d30151f2eb
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.