LTC/BTC · swap

468cf9e2-bf57-4bd6-968d-aab1e2f6ba0f

Sell · 2026-06-17 19:16:42 UTC ·

What was traded
Price0.00068457087 BTC
LTC amount5.5644
BTC amount0.003809
≈ USD$248.57
outside the lookback window
How long it took
Started2026-06-17 19:04:46 UTC
Finished2026-06-17 19:16:42 UTC
Took11m 56s

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:2050] !wait for maker payment spend confirmations: rpc_clients:119] Waited too long until 1781757987 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 f9293e2176b9214bd58667069c0f44de42705a739ea90edd2222bfe01c85cb7b. Checked 2026-09-24 17:14:17 UTC.

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

abbeacce5bc4d6c0c2185d2e4c9de1fa4956ea337be33445da67430e92481477

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

  • MakerPaymentSent · MakerPaymentReceived: abbeacce5bc4d6c0c2185d2e4c9de1fa4956ea337be33445da67430e92481477
  • MakerPaymentSpent: f9293e2176b9214bd58667069c0f44de42705a739ea90edd2222bfe01c85cb7b
✓✓✓taker leg · LTC-segwitfrom the swap record

242fa612cb66faaa54b14b4732be9be0d03259bbc4e6240a9efd04f3f5a43572

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

  • TakerFeeSent · TakerFeeValidated: b87b2ca78fa412561550ae9c44f05501faf2962a84322a7100bcc4591d75ac85
  • TakerPaymentSent · TakerPaymentReceived: 242fa612cb66faaa54b14b4732be9be0d03259bbc4e6240a9efd04f3f5a43572
  • TakerPaymentSpent: 4e538634e59afe65cc1022f7db7f18114e02c79bea5472a884572c6fe19fab56
Who traded
20feb427
Taker3bfc79b3
Maker clientDEVDOCS_CLI
Taker clientkomodo-defi-flutter-auth
Versions2.6.0-beta_a12695e · 2.6.0-beta_475cdb4
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.