WJK/DOGE · swap

501b8393-8b40-405d-a5b9-12d30f1befab

Sell · 2026-04-14 16:10:40 UTC ·

What was traded
Price0.01010759 DOGE
WJK amount2,861
DOGE amount28.9135
≈ USD$2.72
outside the lookback window
How long it took
Started2026-04-14 16:10:40 UTC
Finished2026-04-17 20:14:31 UTC
Took3d 04h

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:2052] !wait for maker payment spend confirmations: rpc_clients:119] Waited too long until 1776194539 for transaction to be confirmed 2 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 d9cd39397de48c90ae371886fac4d1615bac9dde5434ab9f139547d7ecdefe7d. Checked 2026-09-24 02:06:33 UTC.

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

3b88b18ed2e0298a5ffbc58e4b0f08eb4115dbe1a9342a1cdb28ab5314017cbc

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

  • MakerPaymentSent · MakerPaymentReceived: 3b88b18ed2e0298a5ffbc58e4b0f08eb4115dbe1a9342a1cdb28ab5314017cbc
  • MakerPaymentSpentByWatcher: d9cd39397de48c90ae371886fac4d1615bac9dde5434ab9f139547d7ecdefe7d
✓✓✓taker leg · WJKfrom the swap record

6947c38b8962bbf05ce8b810b8bf4975d2a4e7b5280c79b4c46d37330aac8582

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

  • TakerFeeSent · TakerFeeValidated: 6fb9127860560b504ce6e64affda4f306ef0a5c61cf84dea173254fd8b4d97c5
  • TakerPaymentSent · TakerPaymentReceived: 6947c38b8962bbf05ce8b810b8bf4975d2a4e7b5280c79b4c46d37330aac8582
  • TakerPaymentSpent: e10c06fe8837d723498685ac8f351d776e08bc68d0b45bbb9c1d73f674bd9e64
Who traded
616be328
Takerunknown
Maker clientmympm
Taker client
Versions3.0.0-beta_e686ef3 · 3.0.0-beta_d56a7bc50
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.