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: 11, 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 80ca3ac1568242b7c04c89fc5353579d33c4c1ce2eb23ba94269449a4367075b. Checked 2026-09-22 12:36:23 UTC.
94368be9d0241d0dc87ba813f84fb9359afcb81b1bf12f80aec19a2fa0b0dbeb
Both payments are on their chains and locked to the same secret hash f4b42eeb0dd369b6729e1463631ef087bf7efcff, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 94368be9d0241d0dc87ba813f84fb9359afcb81b1bf12f80aec19a2fa0b0dbeb
5537477df3c875f965e33ac3fe20fcba551e7dc43bbdf107cf249b56eb4e592f
Both payments are on their chains and locked to the same secret hash f4b42eeb0dd369b6729e1463631ef087bf7efcff, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 2953881bba0dae30f0a1771eef899032b4cd6fac61235310308a1a247772f929
- TakerPaymentReceived · 5537477df3c875f965e33ac3fe20fcba551e7dc43bbdf107cf249b56eb4e592f
- TakerPaymentSpent · c992a52fba50275fb2e3053b41f00d5b7f4e1d585d37c427a0b6cfa316e38be1
No anomalies were recorded against this swap.
Reported by defistats-gleec.