That is in the normal range for SYS/LTC. The time a swap takes is set mostly by the block spacing of the two chains involved, so a pair with slow blocks is slow for everyone, every time.
The record stops at MakerPaymentSpendFailed. The taker's claim on the maker's coin was rejected; it can be retried while the timelock holds.
taker_swap:2010] mm2src\coins\utxo\ "utxo_common:1025] utxo_common:977] client:985] JsonRpcError { client_info: "coin: LTC-segwit", request: JsonRpcRequest { jsonrpc: "2.0", id: 10, method: " ", params: }, error: Internal("All servers errored: [(, Transport(\"Failed to establish connection: Tempora…
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 be retried for as long as the timelock holds, and whether it was 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 79202a3cebcbbbd23372f6e403e5c7206f93ed07af58c96c7ba38019af475365. Checked 2026-09-22 12:36:22 UTC.
f2250446cc829847b33732dfb4059b3957c33b68ff3dbc4a149557ca6e67d53b
Both payments are on their chains and locked to the same secret hash 67c5cfac29a783621c4e7b654a845534d81939e6, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · f2250446cc829847b33732dfb4059b3957c33b68ff3dbc4a149557ca6e67d53b
35c8d832b9f816f23b76bdfc6cac84e7379830273bae1c48ff76525eecc6e6d5
Both payments are on their chains and locked to the same secret hash 67c5cfac29a783621c4e7b654a845534d81939e6, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 3c3f08ad2d04e1cb00e38722ef720f6b7d8617d73e7c85a8170bd517cc3e6f62
- TakerPaymentReceived · 35c8d832b9f816f23b76bdfc6cac84e7379830273bae1c48ff76525eecc6e6d5
- TakerPaymentSpent · 229786f0d016f71e71a7475db7db75ea5ca2d1ae7e2ff3004c314934025e460d
No anomalies were recorded against this swap.
Reported by defistats-gleec.