MCL/PND · swap

d2393a3b-9c1b-41a5-85a8-97f5fcc3f84b

Buy · 2025-11-02 22:17:38 UTC ·

What was traded
Price98.3917 PND
MCL amount337.9456
PND amount33,251
≈ USD$2.78
outside the lookback window
How long it took
Started2025-11-02 21:55:09 UTC
Finished2025-11-02 22:17:38 UTC
Took22m 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 MakerPaymentSpendConfirmFailed. The taker's claim on the maker's coin was broadcast but not seen to confirm.

taker_swap:2044] !wait for maker payment spend confirmations: rpc_clients:119] Waited too long until 1762132009 for transaction to be confirmed 5 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 05d460a5d6c3d4075f6eb1a3643bd4b9ce0b005e8a3c65a3d085f3c81128c50c. Checked 2026-09-22 12:51:54 UTC.

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

7c9486121be6856c72716b3d3f25d1285910b5239fa734b52052ed01a07af153

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

  • MakerPaymentSent · MakerPaymentReceived: 7c9486121be6856c72716b3d3f25d1285910b5239fa734b52052ed01a07af153
  • MakerPaymentSpent: 05d460a5d6c3d4075f6eb1a3643bd4b9ce0b005e8a3c65a3d085f3c81128c50c
✓✓✓taker leg · PNDfrom the swap record

f10ef159b73d0a9ef3d05d9afd44478d2f0c02b8edf66e4f6138f153fbf914aa

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

  • TakerFeeValidated · TakerFeeSent: 5e7eecb4103831ef333d3169a0bb0b96d70d16d0773946c569bf41aa752741aa
  • TakerPaymentReceived · TakerPaymentSent: f10ef159b73d0a9ef3d05d9afd44478d2f0c02b8edf66e4f6138f153fbf914aa
  • TakerPaymentSpent: 9f115ab31cedeb393345eaea2d7ac69f37aea1e072b520f0173571305b80806c
Who traded
0e4fab2a
Taker72de8c94
Maker clientPandacoin-multiwallet-DEX 0.8.2-beta
Taker client
Versions2.4.0-beta_f56917b · 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.