LCC/USDC · swap

dd4c0acb-db98-476d-b5f9-2e49c3ccc012

Sell · 2026-02-28 12:33:29 UTC ·

What was traded
Price0.00202017 USDC
LCC amount8,165
USDC amount16.4942
≈ USD$16.50
outside the lookback window
How long it took
Started2026-02-28 12:33:29 UTC
Finished2026-02-28 12:35:24 UTC
Took1m 54s

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 MakerPaymentSpendFailed. The taker's claim on the maker's coin was rejected; it can be retried for as long as that payment is unspent.

taker_swap:2008] "eth:2892] request MethodCall(MethodCall { jsonrpc: Some(V2), method: "eth_sendRawTransaction", params: Array([String("0xf9010a4c8402faf08083014c0894edc5b89fe1f0382f9e4316069971d90a0951db3180b8a402ed292b2efd00d853ba592a86ee21ec0852c01d66cbadad4bb143f7532e9a395be49255000000000000000…

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 swap contract records the payment as spent by the receiver. Checked 2026-09-22 15:40:32 UTC.

On-chain evidence
✓✓✓maker leg · USDC-BEP20from the swap record

57e1608cc6cf5f80193acbab98fa5dbe8c8b9bcdc96a348dd76fe1e1ddd3ee95

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

  • MakerPaymentSent · MakerPaymentReceived: 57e1608cc6cf5f80193acbab98fa5dbe8c8b9bcdc96a348dd76fe1e1ddd3ee95
✓✓✓taker leg · LCC-segwitfrom the swap record

283e96915ded6f43f02d85f2833755c5c57a0122fb175014fde00992e6e2ed87

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

  • TakerFeeSent · TakerFeeValidated: 0ce58fc4dfccbd6fff97537cd9069e778421b23ddfb2242203e5ddae1868fb8c
  • TakerPaymentSent · TakerPaymentReceived: 283e96915ded6f43f02d85f2833755c5c57a0122fb175014fde00992e6e2ed87
  • TakerPaymentSpent: b920d226192fe493ffe42cf6c54ae9d4d26679a28ba6ad0a4c57a054624a5f28
Who traded
c28f7f22
Taker03df8286
Maker clientCheetahdex Wallet 0.9.0-beta
Taker client
Versions2.4.0-beta_c800ea03f · 2.6.0-beta_5308356b5
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 defistats-gleec.