This one took about 23.4× the usual for BTCZ/LTC. Waiting longer than usual is not in itself a failure: a swap waits on confirmations from both chains, and a slow block or a busy network stretches it.
The record stops at MakerPaymentSpendConfirmFailed. The taker's claim on the maker's coin was broadcast but not seen to confirm.
taker_swap:2052] !wait for maker payment spend confirmations: rpc_clients:119] Waited too long until 1785169816 for transaction to be confirmed 1 times
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 e88150a7e704471d67147e510c591eaeab9f58fcd964ee4b2f141e0a2a4a12a9. Checked 2026-09-22 12:37:53 UTC.
4c41988485a35353fb150e1e152cfe42de36aa4ba168adf261061948fef7fb26
Both payments are on their chains and locked to the same secret hash b2389615e530670d7eca178b1fe98125ebd7ea92, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · 4c41988485a35353fb150e1e152cfe42de36aa4ba168adf261061948fef7fb26
bac5fc38b17732c7f17abc267847fc4d2f98b59769257cf70d0c0f27ba45ed73
Both payments are on their chains and locked to the same secret hash b2389615e530670d7eca178b1fe98125ebd7ea92, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 47fe11cd38187cbf21ed710b900220b244967e2e5218cebd94b9371582a08351
- TakerPaymentReceived · bac5fc38b17732c7f17abc267847fc4d2f98b59769257cf70d0c0f27ba45ed73
- TakerPaymentSpent · 060d1a8fa2d1e743cbec13fd6df700c78534df6e533ec3d2dbd052cd14feb51d
No anomalies were recorded against this swap.
Reported by defistats-gleec.