FIX/DGB · swap

565aa2a5-da12-4f3d-8e43-645923940b22

Buy · 2026-07-23 16:25:46 UTC ·

What was traded
Price849.2437 DGB
FIX amount0.002669
DGB amount2.2665
≈ USD$0.007704
outside the lookback window
How long it took
Started2026-07-23 16:25:41 UTC
Finished2026-07-24 06:37:22 UTC
Took14h 11m

An atomic swap is not instant by design. Each side has to publish a transaction and wait for the other chain to confirm it, so the time it takes is set mostly by the block spacing of the two chains involved rather than by anything either party does.

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:2050] !wait for maker payment spend confirmations: rpc_clients:119] Waited too long until 1784835440 for transaction to be confirmed 3 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 9d1747137871cd205d4d6af2f3969ee70f846e2ba303a9b964908bd603017ef8. Checked 2026-09-22 12:37:59 UTC.

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

3d02783b6888835681c4c5a80020dccbcf4da1aac5622d5cb91eaef77275939f

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

  • MakerPaymentReceived · MakerPaymentSent: 3d02783b6888835681c4c5a80020dccbcf4da1aac5622d5cb91eaef77275939f
  • MakerPaymentSpent: 9d1747137871cd205d4d6af2f3969ee70f846e2ba303a9b964908bd603017ef8
✓✓✓taker leg · DGB-segwitfrom the swap record

f2c9bdec30c63118e573341d7402793ad2603754cc7ca52149b0ec5a5dc7d87a

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

  • TakerFeeSent · TakerFeeValidated: ce177ecda139018616e4b2ada1beb07f05307786ee0dc8030c4449cc68c6d173
  • TakerPaymentSent · TakerPaymentReceived: f2c9bdec30c63118e573341d7402793ad2603754cc7ca52149b0ec5a5dc7d87a
  • TakerPaymentSpent: ab9407cf61657582889a091067bf17e47aa4aebf479b978bc48a892b6c851f15
Who traded
49141db2
Takera9f8d750
Maker clientDEVDOCS_CLI
Taker client
Versions2.6.0-beta_a12695e · 2.6.0-beta_475cdb49b
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.