@BabylonLabs_io I kept getting stuck on one small design decision in Babylon's TBV filing with Aave DAO — the choice to never let vaultBTC become transferable.

The protocol needs a way to represent locked Bitcoin inside the borrowing system, but doesn't turn that representation into something people can freely pass around. vaultBTC is minted one-to-one against a vault, restricted so it only interacts with Aave's own Hub, Spoke, and adapter contracts. Nowhere else. $BEAT

That felt intentional. It isn't even Babylon's first time making this choice. Months earlier, an experimental version tested on Morpho worked differently at the mechanism level, built as a non-fungible asset rather than an ERC-20, with liquidity of just $14 in USDC. Co-founder David Tse called it "an intermediate non-fungible asset that interfaces the vault with Morpho." Different mechanism, same instinct: never let the representation outgrow the one integration it was built for.

If vaultBTC became tradable, a second market would form around the collateral representation itself, separate from the Bitcoin backing it. That's the actual reason it stays non-transferable — it stops the collateral from taking on a life of its own.

I actually appreciate that restraint. Not every protocol needs another circulating token, even at the cost of flexibility.

Imagine GRVT's Unified Margin — where one deposit already earns yield through Aave, backs trades, and holds spot exposure at once — trying to absorb vaultBTC the same way. It couldn't. Even a platform already plugged into Aave would need its own separate vault. Never made transferable, on purpose. $GRVT

Sometimes limiting what users can do is exactly how a protocol protects its assumptions.

Is non-transferability the cleaner design, or does it sacrifice too much for the composable future DeFi is building toward?

@BabylonLabs_io $BABY #baby