VRSC/USDC · swap

b6e01fbf-6ed9-4297-b7cb-1791faf89284

Sell · 2026-02-03 09:52:55 UTC ·

What was traded
Price0.87915132 USDC
VRSC amount3.0477
USDC amount2.6794
≈ USD$2.68
outside the lookback window
How long it took
Started2026-02-03 09:52:55 UTC
Finished2026-02-03 12:13:35 UTC
Took2h 20m

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:2008] eth:4545] Payment SignedTransaction { transaction: Eip1559(UnverifiedEip1559Transaction { unsigned: Eip1559Transaction { chain_id: 137, nonce: 4808, max_fee_per_gas: 1044180369816, max_priority_fee_per_gas: 120000000000, gas: 110000, action: Call(0x9130b257d37a52e52f21054c4da3450c7…

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:32 UTC.

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

e8c9ebfb43d6db396a6b11f54b083b425b5d8778760243e488bcf48b666e9549

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

  • MakerPaymentSent · MakerPaymentReceived: e8c9ebfb43d6db396a6b11f54b083b425b5d8778760243e488bcf48b666e9549
✓✓✓taker leg · VRSCfrom the swap record

1a4438a0215d4d4d0b4e28694bca3c0c8d01bb71b0162b8268175e621bf6cb7c

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

  • TakerFeeSent · TakerFeeValidated: d9cff0e722aefa371188cf3fa7de9d6b38a19c4930cbb3d9e8797a20eed3472b
  • TakerPaymentSent · TakerPaymentReceived: 1a4438a0215d4d4d0b4e28694bca3c0c8d01bb71b0162b8268175e621bf6cb7c
  • TakerPaymentSpent: a7e2b56182ead372941d29d3fa4f395b0c156338006decb860f30a08c8403627
Who traded
6374243e
Taker03df8286
Maker clientmympm
Taker client
Versions2.6.0-beta_8404fa5 · 2.6.0-beta_5308356b5
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.