I hope this isn't a repeat of a question previously asked, but has anyone with a test version running been able to model confirmation times? I am not a developer so I am just guessing but it seems confirmations are probabilistic, maybe based on aging of open nodes being merged to rule out doublespends.

Because there is always the possibility of receiving a double spent token, one strategy is to immediately respend the token and hope to receive value before the transaction is potentially invalidated.  If a merge fails because of a conflicting transaction, is the doublespend flagged so future spends aren't mistakenly accepted?

Is there a simple way to explain how the system optimizes merging open nodes to miminize probablistic confirmation?

Sorry it this doesn't make sense but very interested in understanding how it works.

Thanks!