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.
582688396cdaccbbb925858eb95cb52d9c92cb28f5371ab05360b647930b69f9
Both payments are on their chains and locked to the same secret hash b408b913e79a0a6f807a7eb1215908eda84539f5, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 582688396cdaccbbb925858eb95cb52d9c92cb28f5371ab05360b647930b69f9
- MakerPaymentSpent: 947b0d8238ca920ef4f25b0bc35badb559b63933c19699e49ec136f935c4d21a
4ed614adc045dc78bfde807a7019ec1f44d93fe09e21a7b564902555636ed356
Both payments are on their chains and locked to the same secret hash b408b913e79a0a6f807a7eb1215908eda84539f5, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 0b47ce8392bd8dd018415b4dcdb4471c9f489d7b8ac560ba549779b913bdf8cf
- TakerPaymentSent · TakerPaymentReceived: 4ed614adc045dc78bfde807a7019ec1f44d93fe09e21a7b564902555636ed356
- TakerPaymentSpent: 65617ac0ff1a150763a6ec57a412153c5828ad1c0cad92b29d62f97d282c6e5c
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.