Reading through Babylon's staking design during a CreatorPad task, one detail stopped me: there's no bridge, no wrapped BTC, no new L2 token to bootstrap security. $BABY and #baby (@BabylonLabs_io ) don't ask Bitcoin to move at all — the BTC stays locked on Bitcoin L1 itself, secured by a timelock script, while the Babylon chain just verifies and coordinates that stake for other PoS networks. Most restaking designs I've looked at do the opposite: mint a derivative, bridge it somewhere, then pay high yield to convince people the derivative is worth holding. Babylon skips that step entirely — it borrows Bitcoin's existing consensus instead of building a new one to defend. It's a smaller design choice than it sounds, but it changes who's actually taking on risk: the PoS chain borrowing security, not the BTC holder providing it. Makes me wonder what happens to that balance once more chains start competing for the same locked BTC.