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 MakerPaymentSpendFailed. The taker's claim on the maker's coin was rejected; it can be retried for as long as that payment is unspent.
the transaction was rejected by network rules. mandatory-script-verify-flag-failed (Script failed an OP_EQUALVERIFY operation) (code 16)
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 payment is unspent, and until the timelock passes nobody else can touch it. Whether it was retried 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 12bb5f3b2a7c63377c5db4c2ec547093b229162b20814c727c16727717b2263e. Checked 2026-09-25 23:03:17 UTC.
18af16cdcdb058590c5382bff007517823985e8c120291cf78dc5faccd5854f9
confirmed on-chain, locked to this swap's secret hash
- MakerPaymentSent · MakerPaymentReceived: 18af16cdcdb058590c5382bff007517823985e8c120291cf78dc5faccd5854f9
90c77ecd9735fc035facccc9adae3033b165ded17dc2a95339b895be9fbcacb6
hash not checked: 4 servers tried: 3 failed TLS verification, 1 refused the connection
- TakerFeeSent · TakerFeeValidated: 5638a679180a74331c815faa7464599d0f6b9ac361cc2c2096d6286ac0d149ff
- TakerPaymentSent · TakerPaymentReceived: 90c77ecd9735fc035facccc9adae3033b165ded17dc2a95339b895be9fbcacb6
- TakerPaymentSpent: 334b54b46f065d86829da7c04fa18227be14e68ff77c247920b24997bc6b6706
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.