FIRO/QTUM · swap

ea0e83d0-b013-49ed-ae95-2a8d3bdd7519

Buy · 2026-08-02 20:25:34 UTC ·

What was traded
Price1.0074 QTUM
FIRO amount0.4471
QTUM amount0.4504
≈ USD$0.2916
outside the lookback window
How long it took
Started2026-08-02 20:25:34 UTC
Finished2026-08-03 05:25:57 UTC
Took9h 00m
5m 44s

This one took about 94.2× 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 final claim did not go through on the first attempt

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 1785713839 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 34338544a938e309138a20c196dbfe4a5e343d44317fbf0a1901360a2cb3d27b. Checked 2026-09-22 12:36:54 UTC.

On-chain evidence
✓✓✓maker leg · FIROfrom the swap record

396b858dcdc40f2e4b3b3c30fa327f83b75a3d6e674d1623487966122a66c58d

Both payments are on their chains and locked to the same secret hash 34624c9454759c37be3cb636a20f33186de187f4, and a preimage hashing to it was published on chain when one side claimed.

  • MakerPaymentSent · MakerPaymentReceived: 396b858dcdc40f2e4b3b3c30fa327f83b75a3d6e674d1623487966122a66c58d
  • MakerPaymentSpent: 34338544a938e309138a20c196dbfe4a5e343d44317fbf0a1901360a2cb3d27b
✓✓✓taker leg · QTUMfrom the swap record

9301d6bf0a118a544834a870257dd54c61b9848b1587adfb1ed1b1a4121db115

Both payments are on their chains and locked to the same secret hash 34624c9454759c37be3cb636a20f33186de187f4, and a preimage hashing to it was published on chain when one side claimed.

  • TakerFeeSent · TakerFeeValidated: 48a1a0cb982832c0536f792e9fa593ccf6ca35f462b259a253d73062e63e3f24
  • TakerPaymentSent · TakerPaymentReceived: 9301d6bf0a118a544834a870257dd54c61b9848b1587adfb1ed1b1a4121db115
  • TakerPaymentSpent: ad11a568ef0d82fda4009a1e74897cc646e8775f147f8aa4d09e4431ed241084
Who traded
55a49826
Takere7f73815
Maker clientDEV_CLI
Taker client
Versions2.6.0-beta_475cdb49b · 2.6.0-beta_a12695e
Flags

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.