What stood out wasn't the yield mechanism itself, it was how much of Babylon's actual flow still routes through custodial staking providers rather than the trustless self-custody path the docs lead with. $BABY and #Babylon @BabylonLabs_io are pitched around Bitcoin holders staking directly, no bridging, no wrapping, keeping keys. That's the default narrative. But when I traced actual delegations during the task, a large share sat with a handful of finality providers operating through exchange or custodian integrations, the "advanced" self-run validator path barely used by comparison. One design choice explains a lot of this: the UX for solo staking still assumes real technical comfort with timelocks and signing, while the custodial route is a few clicks. So the people benefiting first are the intermediaries positioned to smooth that friction, not necessarily the long-tail BTC holder the project talks about reaching. Makes sense operationally, but it's a quieter story than "unlocking passive Bitcoin." Wonder if that gap closes as tooling matures, or just becomes the permanent shape of it.
@BabylonLabs_io #baby $BABY