CHTA/KMD · swap

d0bb27f0-66d3-413e-b737-1e5d1a81c227

Buy · 2025-07-25 10:35:38 UTC ·

What was traded
Price0.0000546551 KMD
CHTA amount300
KMD amount0.0164
≈ USD$0.000611
outside the lookback window
How long it took
Started2025-07-25 10:35:38 UTC
Finished2025-07-25 10:56:30 UTC
Took20m 52s
10m 12s

This one took about 2.0× the usual for CHTA/KMD. Waiting longer than usual is not in itself a failure: a swap waits on confirmations from both chains, and a slow block or a busy network stretches it.

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:1834] mm2src\coins\utxo\ "utxo_common:941] utxo_common:894] client:1057] UnexpectedEnd"

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-06 05:24:57 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 · CHTAfrom the swap record

73f1809c39b8bc28e305d35de00572966d66bf458d4e8f1c2d5cdb6e2cde4050

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

  • MakerPaymentSent · MakerPaymentReceived: 73f1809c39b8bc28e305d35de00572966d66bf458d4e8f1c2d5cdb6e2cde4050
✓✓✓taker leg · KMDfrom the swap record

d20ec79e55a1591086dd72c9a8543decaac706fd25c4cd44af6f1fa237b63063

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

  • TakerFeeSent · TakerFeeValidated: 140a8a9803138f2e4806aa17acc15f40eab60a0f605ce10c61c8ac9b00d02348
  • TakerPaymentSent · TakerPaymentReceived: d20ec79e55a1591086dd72c9a8543decaac706fd25c4cd44af6f1fa237b63063
  • TakerPaymentSpent: 89d5bc38e3ae6387d000c8c2056c4bf7cedc58c482ad1faa25400dd6f994ad29
Who traded
0901571f
Taker0e7801ba
Maker clientADEX_MICROBOT
Taker client
Versions2.5.0-beta_fbab8ec · 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.