FIRO/PPC · swap

d7459082-21eb-4e6f-8814-7d6067e50991

Buy · 2026-09-05 23:00:37 UTC ·

What was traded
Price3.1814 PPC
FIRO amount0.692
PPC amount2.2014
≈ USD$0.6318
outside the lookback window
How long it took
Started2026-09-05 23:00:37 UTC
Finished2026-09-06 02:21:13 UTC
Took3h 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 MakerPaymentSpendConfirmFailed. The taker's claim on the maker's coin was broadcast but not seen to confirm.

taker_swap:2052] !wait for maker payment spend confirmations: rpc_clients:119] Waited too long until 1788660737 for transaction to be confirmed 1 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 e2bec17861b193da387a02924f35b5b04879eda1b900862fbebd0c3cbc571051. Checked 2026-09-22 12:35:44 UTC.

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

8122afc9b2aa8b31def468f6c1c823392b7ac8d475873bd1db6493bbfad0208f

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

  • MakerPaymentSent · MakerPaymentReceived: 8122afc9b2aa8b31def468f6c1c823392b7ac8d475873bd1db6493bbfad0208f
  • MakerPaymentSpent: e2bec17861b193da387a02924f35b5b04879eda1b900862fbebd0c3cbc571051
✓✓✓taker leg · PPCfrom the swap record

bb39eb4ee1d38441c6340c4a3fda240ed34c1520e4ee43c30fd0e9676f86114f

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

  • TakerFeeSent · TakerFeeValidated: 0c61aa24e22f081377e8556ef96995d74316eb84d751f048d20a08efba4024e5
  • TakerPaymentSent · TakerPaymentReceived: bb39eb4ee1d38441c6340c4a3fda240ed34c1520e4ee43c30fd0e9676f86114f
  • TakerPaymentSpent: c92a86e0c02a2707a4e2a5dce3f9d7b8d5ee20743bdb847d25aafd188aef9188
Who traded
55a49826
Taker80c4a9ac
Maker clientDEV_CLI
Taker client
Versions2.6.0-beta_475cdb49b · 2.6.0-beta_a12695e
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.