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.
0a957cefb333b36ae7c7e5c4ae272b30a771dfc5b4b70c4d557ba43b5bb65b39
Both payments are on their chains and locked to the same secret hash bf1635ef0a50238945338bfd876e12d05ce07c66, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 0a957cefb333b36ae7c7e5c4ae272b30a771dfc5b4b70c4d557ba43b5bb65b39
- MakerPaymentSpent: 5b7415a87aa0ae264be860b88dc2c2ea386dd0c54f026b13f4a6f705d955c5ee
95aa7da3ceaa0452157e79a7260c77598d8f3ef20cc7db2d62ee674e867bb603
Both payments are on their chains and locked to the same secret hash bf1635ef0a50238945338bfd876e12d05ce07c66, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: 0db3a72752f1ab2d5bddf62fa4cd38e073a97fc0bb8e5c5ba7930861cb8faf8f
- TakerPaymentSent · TakerPaymentReceived: 95aa7da3ceaa0452157e79a7260c77598d8f3ef20cc7db2d62ee674e867bb603
- TakerPaymentSpent: 00e166ce21bbfcf315045904be5fe3f4e2275a95a65dd1d3585547370ef54553
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.