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.
a3f2dd2ec7058abe8c529fd6f147a59e2ee0fa090066741fb7292ee4fabf64d5
Both payments are on their chains and locked to the same secret hash 768b638a77412d36950b6f4f8c79fea1240875af, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: a3f2dd2ec7058abe8c529fd6f147a59e2ee0fa090066741fb7292ee4fabf64d5
- MakerPaymentSpent: 88acc4db200dac673ac0433a51d298f229aac4e016d50112fa1370caa7053d35
755e6b3a6e1774c80cac3bb2dd72b7656f3aa98680549f4ded1a0e3fa9304f40
Both payments are on their chains and locked to the same secret hash 768b638a77412d36950b6f4f8c79fea1240875af, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · TakerFeeSent: df194ca5e2156ee98aaee8939050777bec9849a6fccf63e732f1954a0f3bb186
- TakerPaymentSent · TakerPaymentReceived: 755e6b3a6e1774c80cac3bb2dd72b7656f3aa98680549f4ded1a0e3fa9304f40
- TakerPaymentSpent: e658bee6337f4d0cc40d217859f83e4836e26c74d2d59a562f7cd409b3c98a23
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.