SYS/XVG · swap

ca0c311e-4666-4c25-bd09-2303460ca2ab

Buy · 2025-12-19 21:53:44 UTC ·

What was traded
Price3.4629 XVG
SYS amount28.7624
XVG amount99.6005
≈ USD$0.4873
outside the lookback window
How long it took
Started2025-12-19 21:26:29 UTC
Finished2025-12-19 21:53:44 UTC
Took27m 15s

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 1766191087 for transaction to be confirmed 5 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 2e7e34b87c2bb1c7ef4dac49eb56f3f113f851e6c5308cafd26fe4dc83172a9d. Checked 2026-09-24 18:24:16 UTC.

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

4bad0156a7cd7a43656b8748f9a275dd284229fae76cab6588f78f820d72e424

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

  • MakerPaymentSent · MakerPaymentReceived: 4bad0156a7cd7a43656b8748f9a275dd284229fae76cab6588f78f820d72e424
  • MakerPaymentSpent: 2e7e34b87c2bb1c7ef4dac49eb56f3f113f851e6c5308cafd26fe4dc83172a9d
✓✓✓taker leg · XVGfrom the swap record

44434f4fb91b8d2e522e87be3c314f1255357d3db8a8c0cec1908052d63df513

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

  • TakerFeeSent · TakerFeeValidated: 339ad259a49674969b510ee3f34c49c223ce05522bbc83328083cc119197ed5c
  • TakerPaymentSent · TakerPaymentReceived: 44434f4fb91b8d2e522e87be3c314f1255357d3db8a8c0cec1908052d63df513
  • TakerPaymentSpent: 25e323eacd130609e53e2e8b3979351a5bcc0efb5626170fb9ba05bf71af951c
Who traded
19a2fb83
Takerc729a6fa
Maker clientmympm
Taker clientKomodo Wallet 0.9.2 Android; BT=1738638986
Versions2.6.0-beta_e9d4519 · 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 kdf-statsdb-8762.