BCH/USDC · swap

3043d3c5-8f5e-4e6b-9ff5-6cd9208b00aa

Buy · 2025-11-02 07:36:30 UTC ·

What was traded
Price553.0058 USDC
BCH amount0.03063
USDC amount16.9386
≈ USD$16.93
outside the lookback window
How long it took
Started2025-11-02 07:29:08 UTC
Finished2025-11-02 07:36:30 UTC
Took7m 22s

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:1872] !wait for maker payment spend confirmations: rpc_clients:112] Waited too long until 1762103454 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 3fe87ec3f9137a7b8ec8de06e69ee9c8827670f078ea2347f81342bd8c81f90a. Checked 2026-09-22 12:52:10 UTC.

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

1994c0f5b618bb823568d498931afae1b36729450561b885e3b4d23614b9ac24

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

  • MakerPaymentSent · MakerPaymentReceived: 1994c0f5b618bb823568d498931afae1b36729450561b885e3b4d23614b9ac24
  • MakerPaymentSpent: 3fe87ec3f9137a7b8ec8de06e69ee9c8827670f078ea2347f81342bd8c81f90a
✓✓✓taker leg · USDC-PLG20from the swap record

bc57489cffba5fade6562a43979deb2b4dba442c492fc443a7ee85b6b53cfa5e

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

  • TakerFeeSent · TakerFeeValidated: 91386d15b203cfc1cc114ef7ba14f0cc0308ff7ce4b1fa5dfd46fb960403504f
  • TakerPaymentSent · TakerPaymentReceived: bc57489cffba5fade6562a43979deb2b4dba442c492fc443a7ee85b6b53cfa5e
  • TakerPaymentSpent: a5df22ac181f834a05a754f676e76ca258d2daa9531eb04bdabe0375005f395f
Who traded
6374243e
Taker4877cbb3
Maker clientmympm
Taker client
Versions2.5.2-beta_7a22854 · 2.3.0-beta_2.1.25_gs/v2.3.0-beta_8206c6ef6_Windows_NT_Release
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.