WHIVE/DGB · swap

eece3648-b3bf-4c95-9dd9-4bff61d8de50

Sell · 2024-04-16 00:50:16 UTC ·

What was traded
Price0.023388572 DGB
WHIVE amount0.2347
DGB amount0.005488
≈ USD—
outside the lookback window
How long it took
Started2024-04-16 00:43:53 UTC
Finished2024-04-16 00:50:16 UTC
Took6m 23s

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 MakerPaymentSpendFailed. The taker's claim on the maker's coin was rejected; it can be retried for as long as that payment is unspent.

taker_swap:1803] utxo_common:2035] HTLC spend fee 10000000 is greater than transaction output 548843

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 be retried for as long as the payment is unspent, and until the timelock passes nobody else can touch it. Whether it was retried is a question for the chain rather than for this log.

The chain shows the maker's payment still sitting in its contract: neither claimed nor refunded. The maker had already collected the taker's payment by this step, so the taker paid and has not received the maker's coin. The secret is public, so the taker's claim can still be made; the maker can take it back after the timelock. Checked 2026-11-16 08:13:53 UTC. It will be asked again.

Wondering whether this one is yours? SwapScope cannot tell you: the parties are salted hashes, so that nobody can test a key against this data, and that cuts both ways. Search this swap's uuid in your own wallet's swap history, or open the payment transaction above on a block explorer and see whether the address paying into it is one of yours.

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

254c15f4bf9c1cd126296effe5d40a52d18f51573426bee7b751e4a8892727fc

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

  • MakerPaymentReceived · MakerPaymentSent: 254c15f4bf9c1cd126296effe5d40a52d18f51573426bee7b751e4a8892727fc
✓✓✓taker leg · WHIVE-segwitfrom the swap record

a59f072e2c888229f55215e03496b11a3866a008ce87d5648d597baf332e1ed5

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

  • TakerFeeSent · TakerFeeValidated: 692b06b9a2d674d2aa95b08cab5c9adb779bb3b11af5d311d228c602fab3cca0
  • TakerPaymentSent · TakerPaymentReceived: a59f072e2c888229f55215e03496b11a3866a008ce87d5648d597baf332e1ed5
  • TakerPaymentSpent: 603b27ad56dd10da12dd4051446ef7a3975294d9d0859bb91ec303988ec47253
Who traded
7cca7b82
Taker935eefd7
Maker clientnot reported
Taker clientnot reported
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 kdf-statsdb-8762.