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.
The record stops at MakerPaymentSpendConfirmFailed. The taker's claim on the maker's coin was broadcast but not seen to confirm.
taker_swap:2052] !wait for maker payment spend confirmations: rpc_clients:119] Waited too long until 1789834803 for transaction to be confirmed 2 times
By this step both payments were on their chains and the price had been struck, so the trade counts toward the reference price. The claim can be retried for as long as the timelock holds, and whether it was is a question for the chain rather than for this log.
The chain says the claim landed: the payment was spent with the preimage, in 3e1dabfd8d53306ca452a6c7d66bf3dbb7417a3d9f6eb7c723abb1fa74ad34c9. Checked 2026-09-22 12:35:25 UTC.
e1d09ca884d3a0a33428d0accbee12946594e32ff8a2a2f70f72f03ee19640af
Both payments are on their chains and locked to the same secret hash 1797bc91ca2351cc35f0fea9676ee184954f5d4f, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · e1d09ca884d3a0a33428d0accbee12946594e32ff8a2a2f70f72f03ee19640af
a2f7545684bf4f07121959cb51cc009bcc8615f616703afab80819fd17cae3ac
Both payments are on their chains and locked to the same secret hash 1797bc91ca2351cc35f0fea9676ee184954f5d4f, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated · 565935ff2b376ff1f78ecf217555fbb1a3059e52170cf8b078277fe9fdec9f24
- TakerPaymentReceived · a2f7545684bf4f07121959cb51cc009bcc8615f616703afab80819fd17cae3ac
- TakerPaymentSpent · 1eb44a70a5d72857ffaf2c059a5ecdf7a2ce75b985baf1c440072f06a1d36dae
Reported by kdf-statsdb.