What caught my attention on Babylon’s Trustless Bitcoin Vaults (TBV) testnet was that four Vault Provider pages showed the same 1% commission, but success rates ranged from 14.2% to 49.2%. At first, that looked like a ranking. The mechanism made me read it differently. Because these are changing testnet figures, I would use them to guide questions, not settle a verdict about mainnet reliability.
A vault has to move from Pending to Verified. During this stage, the Vault Provider and operators must complete setup and acknowledgements within 24 hours. After that, the depositor must reveal the activation secret on Ethereum before roughly 48 hours so the vault can become Active.
Miss either gate and the final label may be the same: Expired.
That is the detail I would not ignore. One headline success rate can mix two events. One may reflect setup or coordination problems before Verified. Another may reflect a user who received a ready vault but never completed activation. So the percentage may contain a provider signal, but it does not show who caused each expiry.
For @BabylonLabs_io $BABY testnet, I see a better check in a stage-based funnel: how many requests reach Verified, and how many Verified vaults reach Active. These would be proposed metrics, not official Babylon KPIs.
When testing TBV, record the provider, highest state reached, whether activation was attempted, and final result. “My vault stayed Pending” or “It reached Verified but I did not activate it” gives better feedback than “my provider failed.” #baby
A vault has to move from Pending to Verified. During this stage, the Vault Provider and operators must complete setup and acknowledgements within 24 hours. After that, the depositor must reveal the activation secret on Ethereum before roughly 48 hours so the vault can become Active.
Miss either gate and the final label may be the same: Expired.
That is the detail I would not ignore. One headline success rate can mix two events. One may reflect setup or coordination problems before Verified. Another may reflect a user who received a ready vault but never completed activation. So the percentage may contain a provider signal, but it does not show who caused each expiry.
For @BabylonLabs_io $BABY testnet, I see a better check in a stage-based funnel: how many requests reach Verified, and how many Verified vaults reach Active. These would be proposed metrics, not official Babylon KPIs.
When testing TBV, record the provider, highest state reached, whether activation was attempted, and final result. “My vault stayed Pending” or “It reached Verified but I did not activate it” gives better feedback than “my provider failed.” #baby