AUR/RVN · swap

1b7eec43-9fbc-4495-a4cd-163d078be8b8

Sell · 2025-05-03 11:39:34 UTC ·

What was traded
Price2.7771 RVN
AUR amount0.001411
RVN amount0.003919
≈ USD$0.000045
outside the lookback window
How long it took
Started2025-05-03 11:39:34 UTC
Finished2025-05-03 12:03:19 UTC
Took23m 45s

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 1100000 is greater than transaction output 391883

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:58 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 · RVNfrom the swap record

1c7eea40038e67577b18560f81b2f0628a50fd487d16fad5b4d681641d69253b

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

  • MakerPaymentSent · MakerPaymentReceived: 1c7eea40038e67577b18560f81b2f0628a50fd487d16fad5b4d681641d69253b
✓✓✓taker leg · AURfrom the swap record

c5147563077b572c38a9efb271f2622d2b02f5d64e831cabc648718444d1528c

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

  • TakerFeeSent · TakerFeeValidated: 6a186298babed0f356144f015cb2019688b26ede2c8090ad8fd5f75781a589b5
  • TakerPaymentSent · TakerPaymentReceived: c5147563077b572c38a9efb271f2622d2b02f5d64e831cabc648718444d1528c
  • TakerPaymentSpent: e6139b3a6f7ac36d267710dfed9b5deb07c6e5d62bb4ca0f8cb7d78fc4b3beac
Who traded
20feb427
Taker822ce7e8
Maker clientmympm
Taker client
Versions2.4.0-beta_e4b68d6 · 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.