This one took about 143.6× the usual for QTUM/DGB. 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 1788351758 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 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 edac0d8c675e104df34c5320f96e7d05a6b5b562a60866a15033bdfd644deae8. Checked 2026-09-22 12:36:00 UTC.
12cddc3e5399db4baa55678f93e2a0d62eda316a3349b103c817d3f030c6e5a4
Both payments are on their chains and locked to the same secret hash 39c1899999bca64e3a731a7920bd26a549d97c7e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 12cddc3e5399db4baa55678f93e2a0d62eda316a3349b103c817d3f030c6e5a4
- MakerPaymentSpentByWatcher: edac0d8c675e104df34c5320f96e7d05a6b5b562a60866a15033bdfd644deae8
8c71bd79f34e90ce327a4507017e9e4771922ed4c1fbe254cc7a12522294daa2
Both payments are on their chains and locked to the same secret hash 39c1899999bca64e3a731a7920bd26a549d97c7e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 21b3b0c3272a1cba1c763f4d1904442c7f805f664a31c26e02f9f4ca5506945c
- TakerPaymentSent · TakerPaymentReceived: 8c71bd79f34e90ce327a4507017e9e4771922ed4c1fbe254cc7a12522294daa2
- TakerPaymentSpent: b062653a7cacd850eec25817ddc6e9edfab3ca02687565dc242951cf31579f54
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.