This one took about 2.4× the usual for CHTA/DGB. Waiting longer than usual is not in itself a failure: a swap waits on confirmations from both chains, and a slow block or a busy network stretches it.
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.
taker_swap:1915] utxo_common:1904] HTLC spend fee 10000000 is greater than transaction output 2018270
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 still be made for as long as the payment is unspent, and since the timelock has passed the payer can take it back as well, so whichever lands first settles it. Whether it was retried is a question for the chain rather than for this log.
The chain shows the maker's payment still sitting in its contract: neither claimed nor refunded. The maker had already collected the taker's payment by this step, so the taker paid and has not received the maker's coin. The secret is public, so the taker's claim can still be made; the timelock expired 2025-11-09 23:47:46 UTC, so the maker can take it back now. Checked 2026-11-06 04:56:21 UTC. It will be asked again.
Wondering whether this one is yours? SwapScope cannot tell you: the parties are salted hashes, so that nobody can test a key against this data, and that cuts both ways. Search this swap's uuid in your own wallet's swap history, or open the payment transaction above on a block explorer and see whether the address paying into it is one of yours.
aff80c801a74cfbe4f632ccc64fc98f3956438a20cde33a597bf859f26e37a3a
Both payments are on their chains and locked to the same secret hash e1963d75288b727c06a56064690e2382fb51cae7, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent · MakerPaymentReceived: aff80c801a74cfbe4f632ccc64fc98f3956438a20cde33a597bf859f26e37a3a
68b0c9fa972a1c5227b3556dc48d9d7cfd0fffa00fbe2865803e2aeae6b3deb0
Both payments are on their chains and locked to the same secret hash e1963d75288b727c06a56064690e2382fb51cae7, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeSent · TakerFeeValidated: 30d1200bc13246ba8aae3922dae459f594804352261faf95793d7e102b2ff780
- TakerPaymentSent · TakerPaymentReceived: 68b0c9fa972a1c5227b3556dc48d9d7cfd0fffa00fbe2865803e2aeae6b3deb0
- TakerPaymentSpent: aed0669be614c59f69906c71c862b0170e980d5068a4369dc2c7517417f2d888
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 defistats-gleec.