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.
ff29034fee110c3f9eb717b5e11ce7c16b18c87e05e17b09886b303a569cf5ae
Both payments are on their chains and locked to the same secret hash 8bd1d908efe494e8ae834c48d58ab23f574bdfc5, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: ff29034fee110c3f9eb717b5e11ce7c16b18c87e05e17b09886b303a569cf5ae
- MakerPaymentSpent: 6f04f2e96542aabff86cfde4d53b0259676c517b33687fa25853af86784f1dad
89855d967b90f30ae11b0e7874e5bdfcb084be99f15980dad0bafa32cdec123f
Both payments are on their chains and locked to the same secret hash 8bd1d908efe494e8ae834c48d58ab23f574bdfc5, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: ffc39f91a18e889fd52b790ab67b05305465c7eddd89a14d6c2fa0d04dcb51fc
- TakerPaymentSent · TakerPaymentReceived: 89855d967b90f30ae11b0e7874e5bdfcb084be99f15980dad0bafa32cdec123f
- TakerPaymentSpent: f19bac8fc0c65ba0f8aa76c71371fafe1152b1a70cd90bb30b61f197ef7a516e
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.