This one took about 52.9× the usual for FIRO/QTUM. 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 1787650592 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 be3c1195b344855db9f84697e635a5de3451d5e7f6937dba236659e55b377a1d. Checked 2026-09-22 12:36:06 UTC.
c120744eaa0768edd635035c6db2377cf47e5bace5d74c0092ac96a56feb0b62
Both payments are on their chains and locked to the same secret hash 5e01075a8b3094825bd2590ab4dfd26dc62a3d4b, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: c120744eaa0768edd635035c6db2377cf47e5bace5d74c0092ac96a56feb0b62
- MakerPaymentSpentByWatcher: be3c1195b344855db9f84697e635a5de3451d5e7f6937dba236659e55b377a1d
05a0f33b73ba516fe0ac4f50b424d5d19ed85441aa31706fa22c161e1c55d600
Both payments are on their chains and locked to the same secret hash 5e01075a8b3094825bd2590ab4dfd26dc62a3d4b, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: f472d3134ecfb7304f34efce0de99ff90d2d426716104fe5d6e891e24a7385b4
- TakerPaymentSent · TakerPaymentReceived: 05a0f33b73ba516fe0ac4f50b424d5d19ed85441aa31706fa22c161e1c55d600
- TakerPaymentSpent: 8c14b5f789d0435ccfdfe5017dad36db23d1ae95ce0ca2456b467f74f1fbf028
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.