i've been sitting with one detail in babylon’s TBV design that i haven’t seen anyone actually poke at

the pitch is that BitVM3 removes the old signer-committee model entirely, redemption gets controlled directly by two predefined parties instead of a group that could collude. fine, that solves the collusion problem. but nobody’s really asking the next question: what happens if one of those two predefined parties just… isn’t around when redemption needs to happen?
a committee model has a weird tradeoff built in, more people who could collude, but also more people who could still be reachable if one drops off. going to two predefined parties removes the collusion risk but seems to concentrate liveness risk into fewer points of failure. if one side goes dark at the wrong moment, does the other side actually have a clean path to recover funds, or does the proof/challenge machinery need to do a lot of quiet work to cover that gap?
i don’t have a clean answer here. it might be a total non-issue if the challenge window handles it fine. but “we removed the collusion risk” and “we removed the risk” aren’t the same claim, and i haven’t seen babylon’s docs address the second one directly yet
@BabylonLabs_io $BABY #baby #OilDropsAbout6% #BrentCrudeFallsAbout6%

What matters most?