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.
8a8ae5c450b8a1f0674c2493abd6f3aa1bf585c93a6a66459b4d5cac04f55248
Both payments are on their chains and locked to the same secret hash b7710039fd2d2fc8ff63f1e98099e559091bfa7e, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: 8a8ae5c450b8a1f0674c2493abd6f3aa1bf585c93a6a66459b4d5cac04f55248
- MakerPaymentSpent: 8c5dbd09a885b03816bc5f118d15fbf2fa88bda87d4b868afec807bf45a9e95b
4edb50b02c698c5182263dff4dbd880e01aa3dabfafd70ba82088f0962917726
Both payments are on their chains and locked to the same secret hash b7710039fd2d2fc8ff63f1e98099e559091bfa7e, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: b79274847077bb8fdbf23918a81ef0b36f1e6a9aa9ffcb52dc04e872fb5338fd
- TakerPaymentReceived · TakerPaymentSent: 4edb50b02c698c5182263dff4dbd880e01aa3dabfafd70ba82088f0962917726
- TakerPaymentSpent: d00dd1ef765902d970d62874cdaddb96040052f2a33760ec0573bb8ff3b66cee
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.