Every @BabylonLabs_io explainer repeats the same line: delegate to a finality provider that misbehaves, and your Bitcoin gets slashed. That's presented as the thing making 56,000+ BTC "securing" these chains mean something — real capital at risk if a provider double-signs.
So I checked the actual parameter instead of the warning text. Pier Two's node-operator docs spell it out: double-sign, and the BTC penalty is a fixed 0.1% of the staked amount. Compare that to BABY validators, who lose 5% for the same offense — fifty times the rate.
That gap is what made me stop. The pitch is "Bitcoin's security extends outward," and most people read that as attacking a BSN costing something close to the full BTC behind it, the way serious slashing works on Ethereum. But if the actual deterrent caps at a tenth of a percent, "billions in BTC securing this chain" is doing more narrative work than economic work. A provider misbehaving isn't risking billions — they're risking 0.1% of delegated stake, and that risk sits with the BTC holders who delegated, not the provider's own capital.
Worth noting plainly: no finality provider has actually been slashed on Babylon yet. The mechanism is still untested in production — no real-world check on whether 0.1% keeps 250+ operators honest once real incentives to misbehave show up.
Is 0.1% a deliberate choice to keep delegators' downside small enough that they're willing to stake, or a sign the "security" here is thinner than the TVL headline suggests once you look at what's actually enforceable?

#baby $BABY $BTC