The whitepaper says Bob himself can act as a challenger. No gate, no approval no third party needed. Thats the actual two party vault design in Trustless Bitcoin Vaults (TBV). #baby

But the protocol actors documentation names a specific role called Universal Challenger a single entity that watches every claim across every application. On testnet, that role currently belongs to one named party Altlayer. @BabylonLabs_io

Not saying thats a contradiction exactly. The two party design and the Universal Challenger role might just be describing different deployment scenarios simple vaults versus applications that need broader monitoring.

Not saying its nothing either The whitepaper whole pitch is that either party can challenge without needing anyones permission. Then in practice one specific company ends up holding a role that sounds a lot more centralized than Bob can challenge too.

What I have Not seen explained anywhere is whether Universal Challenger is meant to stay a single entity long term or if thats just how testnet happens to be set up while more challengers get added later.

$SKYAI $BLESS $BABY