VARRR/KMD · swap

c8068d8e-c897-41ab-b36d-21b8627bca69

Buy · 2025-10-11 16:56:59 UTC ·

What was traded
Price8.2663 KMD
VARRR amount0.00311
KMD amount0.02571
≈ USD$0.000913
outside the lookback window
How long it took
Started2025-10-11 16:29:07 UTC
Finished2025-10-11 16:56:59 UTC
Took27m 52s

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:1872] !wait for maker payment spend confirmations: rpc_clients:112] Waited too long until 1760211649 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 7748c81233ca52075fd8cb17f314962610f89c9bece9ae0fecd67dae449e35a4. Checked 2026-09-22 15:49:18 UTC.

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

09f544bbd1e72bfc2d1fef86f4800c341b5fe62b1fcb55e836bd0f41640a7213

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

  • MakerPaymentSent · MakerPaymentReceived: 09f544bbd1e72bfc2d1fef86f4800c341b5fe62b1fcb55e836bd0f41640a7213
  • MakerPaymentSpent: 7748c81233ca52075fd8cb17f314962610f89c9bece9ae0fecd67dae449e35a4
✓✓✓taker leg · KMDfrom the swap record

9adaefc0452696eae62a279b6842a4d23981e9d46c560ce96b8b3065aee3df1d

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

  • TakerFeeSent · TakerFeeValidated: e4204261dc5e98c22f83a5b347965e37b3ac2f67936fadf791d737827111aebb
  • TakerPaymentSent · TakerPaymentReceived: 9adaefc0452696eae62a279b6842a4d23981e9d46c560ce96b8b3065aee3df1d
  • TakerPaymentSpent: 927ba4801f02f3f9eb3cdb9f49ee85fa11eabb1a5726142afaaebf805cd07fa7
Who traded
19a2fb83
Takerb9e6b1f1
Maker clientmympm
Taker client
Versions2.5.2-beta_347d8fc · 2.3.0-beta_2.1.25_gs/v2.3.0-beta_8206c6ef6_Windows_NT_Release
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.