PEP/DOGE · swap

9c17f18f-146d-4959-8947-9aad3433f418

Sell · 2026-05-07 12:34:38 UTC ·

What was traded
Price0.00080455749 DOGE
PEP amount415.459
DOGE amount0.3343
≈ USD$0.03675
outside the lookback window
How long it took
Started2026-05-07 12:34:38 UTC
Finished2026-05-07 16:33:55 UTC
Took3h 59m

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 MakerPaymentSpendConfirmFailed. The taker's claim on the maker's coin was broadcast but not seen to confirm.

taker_swap:2050] !wait for maker payment spend confirmations: rpc_clients:119] Waited too long until 1778168779 for transaction to be confirmed 2 times

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 payment was spent with the preimage, in f697b4d4cb40913a0eb029c4268d5e26ae709cdbfac28309184dd7b465b3f719. Checked 2026-09-22 12:40:02 UTC.

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

f7342bb712227a58d6d818eafd43b45816c0eb7a63bb4386b795b719835b6f1c

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

  • MakerPaymentSent · MakerPaymentReceived: f7342bb712227a58d6d818eafd43b45816c0eb7a63bb4386b795b719835b6f1c
  • MakerPaymentSpent: f697b4d4cb40913a0eb029c4268d5e26ae709cdbfac28309184dd7b465b3f719
✓✓✓taker leg · PEPfrom the swap record

0ae8403b48151a6d9fa173d4f5347cf8a12a8685fcf2934b3e6fb0a280709bfd

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

  • TakerFeeSent · TakerFeeValidated: 2999b9bffca357929c18126d95f4eaef7a670b6ecf2a1abf18ef8ebf79509217
  • TakerPaymentSent · TakerPaymentReceived: 0ae8403b48151a6d9fa173d4f5347cf8a12a8685fcf2934b3e6fb0a280709bfd
  • TakerPaymentSpent: ce89f994e57890a231c38f484795708333a24f93d040b5d06f26d1356e156373
Who traded
aed4b579
Taker104ba9a1
Maker clientDEVDOCS_CLI
Taker client
Versions2.6.0-beta_a12695e · 2.6.0-beta_475cdb49b
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.