LBC/USDT · swap

1f8b578d-d78e-4ca7-a4c3-8e1fe0bf2409

Sell · 2025-11-10 20:14:50 UTC ·

What was traded
Price0.0008 USDT
LBC amount16,000
USDT amount12.8
≈ USD$12.80
outside the lookback window
How long it took
Started2025-11-10 20:06:51 UTC
Finished2025-11-10 20:14:50 UTC
Took7m 59s

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 TakerPaymentSpendConfirmFailed. The maker's claim on the taker's coin was broadcast but not seen to confirm.

maker_swap:1322] !wait for taker payment spend confirmations: rpc_clients:119] Waited too long until 1762824519 for transaction to be confirmed 3 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 86ed1e117d7465eeb7d1d57b9a5c26ff489d8176736df1a9a1390472827fd3d0. Checked 2026-09-24 18:44:13 UTC.

On-chain evidence
✓✓✓maker leg · USDT-PLG20from the swap record

0cf744600f728e0e4d53aa367f86d165f692917c14e39b885f8e4340830c7416

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

  • MakerPaymentReceived · MakerPaymentSent: 0cf744600f728e0e4d53aa367f86d165f692917c14e39b885f8e4340830c7416
  • MakerPaymentSpent: 950a21b766333fa32a7d8d8506c5f1aca245f8f06b8d28495e82633010e02002
✓✓✓taker leg · LBCfrom the swap record

bf79cdb3ce0d182bd0efe820b90a11bd8006892b0ac9b1ab8c823d00d5a9d742

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

  • TakerFeeSent · TakerFeeValidated: fc2c4cd91a2a5751419c23980ed6026003c6a38a0d5badfcbe2e41cf8d563a76
  • TakerPaymentSent · TakerPaymentReceived: bf79cdb3ce0d182bd0efe820b90a11bd8006892b0ac9b1ab8c823d00d5a9d742
  • TakerPaymentSpent: 86ed1e117d7465eeb7d1d57b9a5c26ff489d8176736df1a9a1390472827fd3d0
Who traded
08936d48
Taker8e39003f
Maker clientkomodo-defi-flutter-auth
Taker clientkomodo-defi-flutter-auth
Versions2.5.2-beta_bebdc9a17 · 2.5.2-beta_bebdc9a17
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.