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.
d761cf98c2bee29a7318013a0dd3f7e00b3a20cc61dc35997df1eabbe7d0c23a
Both payments are on their chains and locked to the same secret hash 6ca4dc264e8f0f6b9b12b4d8b56f6a25b8230723, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: d761cf98c2bee29a7318013a0dd3f7e00b3a20cc61dc35997df1eabbe7d0c23a
- MakerPaymentSpent: b200a766d241762bf77e32427a2f10c5e6c98594420976c56c673bf5e9b1551e
6c97a1cf4cb0748eca9ed909aee18f6bf2806a44414330b494ac57d2cf19cf9e
Both payments are on their chains and locked to the same secret hash 6ca4dc264e8f0f6b9b12b4d8b56f6a25b8230723, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: a36172359181c79e1497c28e5d9cc2eeaa12e7124771ba05ac3284076e8f129e
- TakerPaymentReceived · TakerPaymentSent: 6c97a1cf4cb0748eca9ed909aee18f6bf2806a44414330b494ac57d2cf19cf9e
- TakerPaymentSpent: afe3888bbae8e2cc00a7be7bb938a8590a01af009cf825328b0a75b68f6cfdb0
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.