This one took about 2.9× the usual for LBC/DOGE. 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 1793056285 for transaction to be confirmed 2 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 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 04496b0a34a73cb666ff7ff96fa8c0f7f9cb34bae9d665d0b83109a7625acfe0. Checked 2026-10-27 07:20:47 UTC.
da0a29e2ab976f398800f668cf5a20fe180e5c84e017897f026b874a566d1464
Both payments are on their chains and locked to the same secret hash 926fe1721e235117e77d76260f11551fffbf15d4, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: da0a29e2ab976f398800f668cf5a20fe180e5c84e017897f026b874a566d1464
bb8668b9f6a01104dd191e4db8b4cdeee49603fbe84abc22d3f46e1b66739546
Both payments are on their chains and locked to the same secret hash 926fe1721e235117e77d76260f11551fffbf15d4, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: acafb3ba3d5c269682e1ee13afd372af381a478dd930055fa8811b03002c7ef8
- TakerPaymentReceived: bb8668b9f6a01104dd191e4db8b4cdeee49603fbe84abc22d3f46e1b66739546
- TakerPaymentSpent: 95c3a0a812ecae494f1231abff25628d6ded387578b53d7a2b2b7cb7f0a69233
Reported by kdf-statsdb.