AUR/CDN · swap

4f97a5b2-e085-4638-ab9e-abae9a9f20c8

Sell · 2024-07-30 07:24:08 UTC ·

What was traded
Price14.0644 CDN
AUR amount0.5055
CDN amount7.1101
≈ USD—
outside the lookback window
How long it took
Started2024-07-30 07:12:08 UTC
Finished2024-07-30 07:24:08 UTC
Took12m 00s

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.

the transaction was rejected by network rules. 16: mandatory-script-verify-flag-failed (Script failed an OP_EQUALVERIFY operation)

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:53:28 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 · CDNfrom the swap record

32886c961a53c2069f948fb55fd676b52e9bf097f2936050f34f28f57c841b49

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

  • MakerPaymentSent · MakerPaymentReceived: 32886c961a53c2069f948fb55fd676b52e9bf097f2936050f34f28f57c841b49
✓✓✓taker leg · AURfrom the swap record

9446d42aa8abc9181b005f761b4cf729054d3f7e87b83bfc3adaeb649c7629c6

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

  • TakerFeeValidated · TakerFeeSent: 1de82087f67659f6ccf81023b1bc36ca795887ae51173cb6fefd11d2da9c85cd
  • TakerPaymentReceived · TakerPaymentSent: 9446d42aa8abc9181b005f761b4cf729054d3f7e87b83bfc3adaeb649c7629c6
  • TakerPaymentSpent: a1c2e3c4605e9b9d7d465dfb99ee0b9cbe34754ecb53ac0640726315dd7c0829
Who traded
143e0a51
Takeradf20f9a
Maker clientKomodo Wallet 0.7.1-beta
Taker clientKomodo Wallet 0.9.2 Android; BT=1719905944
Versions2.0.0-beta_b0fd99e · 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 kdf-statsdb-8762.