VTC/DGB · swap

f15f6888-102b-4fea-a897-e334bf45af98

Sell · 2026-05-04 10:34:11 UTC ·

What was traded
Price11.9621 DGB
VTC amount128.3333
DGB amount1,535
≈ USD$5.75
outside the lookback window
How long it took
Started2026-05-04 10:34:11 UTC
Finished2026-05-04 13:46:07 UTC
Took3h 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:1909] !wait for maker payment spend confirmations: rpc_clients:112] Waited too long until 1777902351 for transaction to be confirmed 7 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 50b8056798f69d5a538556dd9c41b166944e4b13c9c09ceeb2472e2bd0e0be3c. Checked 2026-09-22 12:40:07 UTC.

On-chain evidence
✓✓✓maker leg · DGB-segwitfrom the swap record

f5a4bcf25fa4df8dc158ba115ffd623d721c2b2a6d12cb4d71c8f3542567a2b9

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

  • MakerPaymentSent · MakerPaymentReceived: f5a4bcf25fa4df8dc158ba115ffd623d721c2b2a6d12cb4d71c8f3542567a2b9
  • MakerPaymentSpent: 50b8056798f69d5a538556dd9c41b166944e4b13c9c09ceeb2472e2bd0e0be3c
✓✓✓taker leg · VTC-segwitfrom the swap record

f4723c7ba906da515dc489b46fdc0ae61ec7f1b8100bbaa9db0f103e83cc31f4

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

  • TakerFeeSent · TakerFeeValidated: 9e7a838248b21a99a5372954b26acc618d5b783cb2f389972c9a7aa15fa71219
  • TakerPaymentSent · TakerPaymentReceived: f4723c7ba906da515dc489b46fdc0ae61ec7f1b8100bbaa9db0f103e83cc31f4
  • TakerPaymentSpent: 647a4b10546cc13b1191a8333005f8bb93cac9d87b5961a86cda2788104aa067
Who traded
6374243e
Takerc729a6fa
Maker clientDEVDOCS_CLI
Taker client
Versions2.6.0-beta_a12695e · 2.3.0-beta_73e0650
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.