FIRO/FJC · swap

5eee9e7f-be51-4d80-9bbd-a9bc666ff16d

Sell · 2025-07-27 18:13:03 UTC ·

What was traded
Price0.08333331 FJC
FIRO amount0.1749
FJC amount0.01457
≈ USD$0.00
outside the lookback window
How long it took
Started2025-07-27 18:13:03 UTC
Finished2025-07-27 18:22:29 UTC
Took9m 27s

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:1803] utxo_common:2035] HTLC spend fee 5235873 is greater than transaction output 1457247

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 07:13:43 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

042eef9c082a8e63c1a57467e809d5349becac5837b95fc9006036deded416b7

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

  • MakerPaymentSent · MakerPaymentReceived: 042eef9c082a8e63c1a57467e809d5349becac5837b95fc9006036deded416b7
✓✓✓taker leg · FIROfrom the swap record

5826ce2e24c66615055a295cd110680d5537a9662e1a138eb036e59dae66131d

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

  • TakerFeeSent · TakerFeeValidated: 76df763cf93b7feabeb3847e0ac766da2a7f002d7c29c4c16c3eb1fcc493e416
  • TakerPaymentSent · TakerPaymentReceived: 5826ce2e24c66615055a295cd110680d5537a9662e1a138eb036e59dae66131d
  • TakerPaymentSpent: 02c6809fd12fbeb610a73e622b377d30983dd00792e223cf27c5160073e98f10
Who traded
9f6a6fce
Taker105ae74e
Maker clientKomodo Wallet 0.8.1-beta
Taker client
Versions2.3.0-beta_2.1.41_gs/v2.3.0-beta_8206c6ef6_Linux_Release · 2.0.0-beta_b0fd99e
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.