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=4442680, 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 a5aacd55ee34d6053f9003641707b641a2cc0560089f1237221a2168619c85a4. Checked 2026-09-22 12:38:36 UTC.
5c44b1a77988da608980ce9b7d2191a83e5a3f0af02cb8882a9b38bc7afb8407
Both payments are on their chains and locked to the same secret hash af3d66211ee4c416eb42a47977e08883dd514d0a, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 5c44b1a77988da608980ce9b7d2191a83e5a3f0af02cb8882a9b38bc7afb8407
c966266785b17624ff21c8c731ab1fae05bee681f6ebe764e58100e015f2ad11
Both payments are on their chains and locked to the same secret hash af3d66211ee4c416eb42a47977e08883dd514d0a, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: b8051e4cf31e14c540986b3b2d705a6b0a5eece87ef50bcebdc7df4d0296645e
- TakerPaymentSent · TakerPaymentReceived: c966266785b17624ff21c8c731ab1fae05bee681f6ebe764e58100e015f2ad11
- TakerPaymentSpent: 1215fe0ae13627e199bb04e27b73a44ae2a8f934200494d920dce6c184490d53
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.