LTC/BTC · swap

bb84da4b-ce3f-4c05-b52a-14742c5f73af

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

What was traded
Price0.00068371488 BTC
LTC amount8.2443
BTC amount0.005637
≈ USD$367.82
outside the lookback window
How long it took
Started2026-06-17 19:05:28 UTC
Finished2026-06-17 19:16:29 UTC
Took11m 01s

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 1781758028 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 caaafbe82408537b1f421767ce50b4e20de5628e3531d42e760ad5898d7b0036. Checked 2026-09-24 17:14:19 UTC.

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

a5e853144ccf3ad72524bd7920fa60e831c5500cef7a49c1af07b1bb92a964b4

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

  • MakerPaymentSent · MakerPaymentReceived: a5e853144ccf3ad72524bd7920fa60e831c5500cef7a49c1af07b1bb92a964b4
  • MakerPaymentSpent: caaafbe82408537b1f421767ce50b4e20de5628e3531d42e760ad5898d7b0036
✓✓✓taker leg · LTC-segwitfrom the swap record

e74db3a456555c1fbef5276fdc17e2c501114e8a85f3f4cce827c61139fd9d60

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

  • TakerFeeSent · TakerFeeValidated: a41da327f9a3ea6db248e233c3c914a6b1e8e13a2152f31db8fed6a9b0a50f1a
  • TakerPaymentSent · TakerPaymentReceived: e74db3a456555c1fbef5276fdc17e2c501114e8a85f3f4cce827c61139fd9d60
  • TakerPaymentSpent: 50d4d531c0bb39c9b33d3cdf3ead768adba29fa8421e8647204291bdee8eae0a
Who traded
709bad88
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.