This one took about 2.1× the usual for VRSC/BCH. 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.
ce3f602a8177b5bb3d86e19bcda52741bb4ed3ffd1a038f33e0089dbdf98fc39
Both payments are on their chains and locked to the same secret hash 08a1a34895f4072f4a9205bd18be086f542df2ee, and a preimage hashing to it was published on chain when one side claimed.
- MakerPaymentSent: ce3f602a8177b5bb3d86e19bcda52741bb4ed3ffd1a038f33e0089dbdf98fc39
8aa4c50399dec6001077efe4080faf371838ba87a30ec9ba3357ce166e269c3a
Both payments are on their chains and locked to the same secret hash 08a1a34895f4072f4a9205bd18be086f542df2ee, and a preimage hashing to it was published on chain when one side claimed.
- TakerFeeValidated: 5fc3f70757b06ff9056ddd81eb491d3e32521c5a0c22b3e9cb2a0542a7150f2d
- TakerPaymentReceived: 8aa4c50399dec6001077efe4080faf371838ba87a30ec9ba3357ce166e269c3a
- TakerPaymentSpent: e0ee076b3e3961dfcfcb1ff57c4284c9ef5427fc1c4756ded947e77369cc5e82
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.