EVR/USDC · swap

b58ae2c2-5065-43fe-8b11-8c0e9ec34b1e

Sell · 2025-11-13 01:13:03 UTC ·

What was traded
Price0.000052100985 USDC
EVR amount20,300
USDC amount1.0577
≈ USD$1.06
outside the lookback window
How long it took
Started2025-11-13 01:04:34 UTC
Finished2025-11-13 01:13:03 UTC
Took8m 29s

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:2002] eth:4545] Payment SignedTransaction { transaction: Eip1559(UnverifiedEip1559Transaction { unsigned: Eip1559Transaction { chain_id: 137, nonce: 4484, max_fee_per_gas: 373053090171, max_priority_fee_per_gas: 45000000000, gas: 110000, action: Call(0x9130b257d37a52e52f21054c4da3450c72f…

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-22 15:40:34 UTC.

On-chain evidence
✓✓✓maker leg · USDC-PLG20from the swap record

064561454ebfa1299a086d459a613acc2a133dbd5a887a99293f3a3dd6ab90b6

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

  • MakerPaymentSent · MakerPaymentReceived: 064561454ebfa1299a086d459a613acc2a133dbd5a887a99293f3a3dd6ab90b6
✓✓✓taker leg · EVRfrom the swap record

f58b4fdbd5e449d82fc439b0071019e914964dfacc820736649ce178e0cdd16a

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

  • TakerFeeSent · TakerFeeValidated: b31103be9c31668757b58c109f304a4a874b5c092df4f869cbf3028f4fc2fcd1
  • TakerPaymentSent · TakerPaymentReceived: f58b4fdbd5e449d82fc439b0071019e914964dfacc820736649ce178e0cdd16a
  • TakerPaymentSpent: c532b596802b168f32e93fd550af0a4dd9b8c8b18ece04c47579f9b40989aa78
Who traded
6374243e
Taker524ac60d
Maker clientmympm
Taker client
Versions2.5.2-beta_2b35f2a · 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 defistats-gleec.