I used the testnet for a week, and I found that TBV’s fixed denominations actually hide an unintuitive design: the more standardized the amount is, the easier it becomes for liquidity to fragment. The 0.01, 0.1, and 1 BTC tiers look clear, but in real use, if you have 0.15 BTC, you can only split it into 0.1 and 0.05. Since 0.05 isn’t a standard denomination, you’d have to switch to BABY to unlock a custom amount—yet custom amounts haven’t even been enabled.

This issue will be magnified even more on the mainnet. When 100,000 token holders all want to lock funds, the extra “dust” created by standardized denominations will大量 settle in wallets instead of entering vaults to earn yield. The only way out is to go to the secondary market to swap for BABY to meet the required denominations. As a result, BABY passively ends up absorbing all liquidity demand from fragmented amounts, with trading volume artificially inflated and price volatility following suit. $BABY $BTC
I started to understand why the official statements say TBV’s ultimate form needs to be paired with a “vault aggregator.” Only by bundling vaults of different denominations into a higher-level financial product can the fragmentation problem be solved. But the aggregator itself requires smart contracts, and in Babylon’s roadmap, this part is still at a very early stage. That means for a considerable period after the mainnet goes live, BABY’s price will repeatedly be affected by these scattered conversion demands, and its volatility may be far higher than that of a typical L2 governance token.

Short-term traders might like this kind of volatility, but for BTC holders who want to lock long-term and earn interest, every spike in BABY is an additional risk exposure. You originally just wanted to earn BTC-denominated yield, but you end up having to take on BABY exchange-rate risk. This hidden cost wasn’t written in any of the promotional copy, but the on-chain data has already made it very clear. #baby @BabylonLabs_io $BABY