I used to like going into the kitchen when the chef was still seasoning—more than when the dish had already been finalized and fixed on the menu 🍲

Back then, everything wasn’t perfect yet; it might still be too salty, not salty enough, even a little clumsy. But precisely because it hadn’t been wrapped up in a layer of finish, I could see more clearly what they were trying to make. Once the dish is on the menu—optimized for the masses—many of its edges and rough spots get smoothed out until they’re hard to recognize. For example, bun dau mam tom (vermicelli with fermented fish sauce); the more rustic, the simpler, the better.

Trustless Bitcoin Vaults’ (TBV) Public Testnet is in exactly that stage.

Most people just want to experience the product once it’s officially live—smooth UI, as streamlined a process as possible. But at that time, what I usually saw was only the polished surface. Now, with the testnet running for more than two months and over 2,000 vaults created, everything is still raw enough to reveal the core design: native BTC is used as collateral on Aave v4; the keys are still held by the users, with no wrapping or bridging.

This is a rare window—not only to test whether the flow works, but to observe whether the promise of “self-custodial + native Bitcoin” holds up when it collides with real users. Feedback at this point carries a completely different weight compared to the later stage, when the product has taken shape and large changes become difficult.

I tried it. The feeling is different from just reading documentation.

What about you? If you had the chance to experience a system while its underlying nature is still clearly visible, which approach would you choose?

#baby $BABY $BICO $TUT @BabylonLabs_io

#USIranTalksToBegin #TrendingTopic