SYS/XVG · swap

ecdc47a3-d2fb-4110-a49d-50782b456e77

Sell · 2025-12-20 01:18:11 UTC ·

What was traded
Price3.3707 XVG
SYS amount85.3692
XVG amount287.7571
≈ USD$1.43
outside the lookback window
How long it took
Started2025-12-20 00:44:57 UTC
Finished2025-12-20 01:18:11 UTC
Took33m 14s

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 1766202999 for transaction to be confirmed 10 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 6aa4a526288ca5487674de9df238d88801b7301c174bb96e4d7e5e5063a9d288. Checked 2026-09-24 18:24:13 UTC.

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

47e521ecda9422e95eea80e5be2d0df045d2a5ca605792dca9c34a3a19adc7bc

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

  • MakerPaymentSent · MakerPaymentReceived: 47e521ecda9422e95eea80e5be2d0df045d2a5ca605792dca9c34a3a19adc7bc
  • MakerPaymentSpent: 6aa4a526288ca5487674de9df238d88801b7301c174bb96e4d7e5e5063a9d288
✓✓✓taker leg · SYS-segwitfrom the swap record

742b990f25fbe0b8bea868f174d9524fb62b91e6418a67451f1af7253230bbe7

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

  • TakerFeeSent · TakerFeeValidated: b9eb42ef9b3b8a33db19014fd77476d98aafae023ef5952a02568499d0569819
  • TakerPaymentSent · TakerPaymentReceived: 742b990f25fbe0b8bea868f174d9524fb62b91e6418a67451f1af7253230bbe7
  • TakerPaymentSpent: 5d1de40504bf0d585ccb25b6e73c2e2c158465294ea5c52d8c496a38b9da5147
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.