GRS/USDC · swap

3105db05-8757-4c39-9dd3-e8c96a4c9d61

Buy · 2025-12-04 19:26:23 UTC ·

What was traded
Price0.15209013 USDC
GRS amount11.7922
USDC amount1.7935
≈ USD$1.79
outside the lookback window
How long it took
Started2025-12-04 19:13:33 UTC
Finished2025-12-04 19:26:23 UTC
Took12m 50s

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

maker_swap:1269] !taker_coin.send_maker_spends_taker_payment: "eth:2892] request MethodCall(MethodCall { jsonrpc: Some(V2), method: "eth_sendRawTransaction", params: Array([String("0x02f901108221050c830f424083571123830249f0944c54808911817402a0871c3c93d8790c19cae75b80b8a402ed292ba256dc1ccfa1e79438d3…

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-24 18:24:17 UTC.

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

4b4b9d5c20cdaeccff6ef38ea83c6a857dcb94f704dfcce8fdf054563473371d

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

  • MakerPaymentSent · MakerPaymentReceived: 4b4b9d5c20cdaeccff6ef38ea83c6a857dcb94f704dfcce8fdf054563473371d
  • MakerPaymentSpent: 86de1cce7b03c4bc614dfed2e41f8950e854d4c2c9a9dac7ab1e73fd8fc50160
✓✓✓taker leg · USDC-BASEfrom the swap record

d37c4c6367ec0445eab9a9eab80944308342641090a7fc061be55d499765960b

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

  • TakerFeeSent · TakerFeeValidated: c188084d9c64ceccc46145e33535550cb9f8c3cf5b05ac00bf08231c9e9743a4
  • TakerPaymentSent · TakerPaymentReceived: d37c4c6367ec0445eab9a9eab80944308342641090a7fc061be55d499765960b
Who traded
20feb427
Taker39a257ae
Maker clientmympm
Taker clientkomodo-defi-flutter-auth
Versions2.6.0-beta_02e7f04 · 2.5.2-beta_bebdc9a17
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.