CHTA/FJC · swap

15ae0f1f-8d02-419a-aaa8-932e2aa37cf2

Sell · 2024-01-18 03:03:37 UTC ·

What was traded
Price0.005 FJC
CHTA amount4.2995
FJC amount0.0215
≈ USD—
outside the lookback window
How long it took
Started2024-01-18 02:37:06 UTC
Finished2024-01-18 03:03:37 UTC
Took26m 31s

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:1761] utxo_common:1765] HTLC spend fee 3450965 is greater than transaction output 2149734

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 be retried for as long as the payment is unspent, and until the timelock passes nobody else can touch it. Whether it was retried is a question for the chain rather than for this log.

The chain shows the maker's payment still sitting in its contract: neither claimed nor refunded. The maker had already collected the taker's payment by this step, so the taker paid and has not received the maker's coin. The secret is public, so the taker's claim can still be made; the maker can take it back after the timelock. Checked 2026-11-16 08:24:02 UTC. It will be asked again.

Wondering whether this one is yours? SwapScope cannot tell you: the parties are salted hashes, so that nobody can test a key against this data, and that cuts both ways. Search this swap's uuid in your own wallet's swap history, or open the payment transaction above on a block explorer and see whether the address paying into it is one of yours.

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

3d392e7c7a8478c971fba61b48fca37f054ee2b61103ca257f09aca02e7c7b6e

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

  • MakerPaymentSent · MakerPaymentReceived: 3d392e7c7a8478c971fba61b48fca37f054ee2b61103ca257f09aca02e7c7b6e
✓✓✓taker leg · CHTAfrom the swap record

3e533862e629f117ba6347dffde437619453af61cb19e5a8902d3e0ca3a13f80

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

  • TakerFeeSent · TakerFeeValidated: f0cc26167ed2f487a851dfa9bf531bdf53152103e5c0442e82de3017f1349172
  • TakerPaymentSent · TakerPaymentReceived: 3e533862e629f117ba6347dffde437619453af61cb19e5a8902d3e0ca3a13f80
  • TakerPaymentSpent: a7a84a718c3eb60a065cb01d6a05924cc3f7383a704cf236a52abf801ef1b90a
Who traded
d98e3d69
Taker6709a355
Maker clientnot reported
Taker clientnot reported
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.