FIX/KMD · swap

da9d37ea-cc45-4e9d-b581-ebf77b123de3

Buy · 2025-10-28 13:26:06 UTC ·

What was traded
Price9,482.78 KMD
FIX amount0.004818
KMD amount45.6872
≈ USD$2.13
outside the lookback window
How long it took
Started2025-10-28 13:00:24 UTC
Finished2025-10-28 13:26:06 UTC
Took25m 42s

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:2044] !wait for maker payment spend confirmations: rpc_clients:119] Waited too long until 1761667924 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 a406a0460a025a185ccfd7a99661f4309279f2fdff71cfd2d628c74c2be317c8. Checked 2026-09-22 12:52:17 UTC.

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

e69a2fb78b2700c0d8e589451902d25bf077d0e718476d912f82110f45e11bcb

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

  • MakerPaymentSent · MakerPaymentReceived: e69a2fb78b2700c0d8e589451902d25bf077d0e718476d912f82110f45e11bcb
  • MakerPaymentSpent: a406a0460a025a185ccfd7a99661f4309279f2fdff71cfd2d628c74c2be317c8
✓✓✓taker leg · KMDfrom the swap record

e95dc7454cc00f23d8e1c31d4748cc12781354586f0e026ebfec3f0dda18a48e

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

  • TakerFeeSent · TakerFeeValidated: 14e73f2cebd214e331bc8ab82f912af7f3eaf66806a12942983178e4948bc98a
  • TakerPaymentSent · TakerPaymentReceived: e95dc7454cc00f23d8e1c31d4748cc12781354586f0e026ebfec3f0dda18a48e
  • TakerPaymentSpent: 17c2dd2c558d60e194de9f2ea9ebe2b59ce5aad185078bd88286be5a1bf2c8e7
Who traded
7cca7b82
Takerf6083882
Maker clientmympm
Taker client
Versions2.5.2-beta_9aa41b4 · 2.5.2-beta_7a22854
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.