老青蛙BNB

That night in July 2023 is one I can never forget. The moment the news that Multichain had blown up spread, a guy in the group went crazy and kept withdrawing coins to the outside. Three-plus BTC that crossed the bridge immediately got stuck. I watched, helplessly, as the project team went from silence to shutting down to being investigated. The money still has no sign of ever coming back. Five years of positioning—one night taught him what it really means when your coin isn’t your own.
Later, when he saw me playing @BabylonLabs_io , he said just one sentence: If this existed a couple of years earlier, why would I have gone through that bridge lesson.
Old veterans have all been educated by the bridge, but many people still haven’t figured out one question to this day: who exactly is the one behind the wrapped BTC you hold—who do you actually trust? Take WBTC as an example. The real BTC is lying in a cold storage in a custodian’s vault. What you receive is essentially a IOU—one note—on Ethereum. Minting depends on the merchants, redemption depends on approvals. Behind every step there are people.
In 2024, when the custodian issued an announcement to split the vault keys with a new joint venture company, Maker turned around and voted to kick WBTC out of its collateral list. A $200 million exposure can be withdrawn just like that. This is the most lethal part of wrapped assets: today you trust A, but tomorrow the keys are handed to B. Trust can change owners in an instant, and you don’t even have a ballot yourself.
The native route is praised by long-time players because Babylon’s TBV answers this problem once and for all. BTC is locked in the vault of the Bitcoin mainnet; pre-signed transactions hardcode the spending path; the external chain only accepts zero-knowledge proofs. Ask who it is you’re supposed to trust—the answer is nobody, don’t trust people, trust math.
The wrapped route is constantly patching the trust chain. The native route directly dismantles the chain. That’s the ultimate difference between the two routes.
Of course, the plain truth is that WBTC’s liquidity and convenience today are still at a crushing level. The depth and ecosystem of the native方案 are still immature. This war isn’t over yet—don’t rush to rotate positions just because someone tells a story.
What the bear market teaches everyone is essentially the same question: are you staking assets on people or on code? Whose are you trusting with that bag of yours—the BTC you hold today? Please pick a seat for yourself. This isn’t investment advice. #baby $BABY

Last Wednesday night, when Strategy’s earnings report came out, my group chat literally exploded. The CEO confirmed in person that the board authorized a maximum of $5 billion worth of bitcoin to be sold. Within just a few hours of the news breaking, BTC smashed through $63,000. One of my friends who was planning to buy the dip got scared and, with a single twitch, closed all his long positions. Then the next day it rebounded and he promptly slapped his own leg. Those “die-hard long” holders of 840,000 BTC apparently even loosened their grip and wanted to sell—no matter who you are, that would make you uneasy. I stared at the chart for most of the night, and then went to @BabylonLabs_io to check that pledged position in the vault again. Good thing—there’s nothing it needs to do.
Let me be fair to MicroStrategy: $5 billion is the authorization limit, not a planned sell order. They said it clearly. The proceeds from selling bitcoin are mainly used to replenish cash reserves and pay preferred-share dividends. This year, the company has bought far more than it has sold, and Saylor has repeatedly emphasized that they’re still net buyers long term. But the problem is that faith isn’t logical. When the iron rule of “only buy, never sell” turns into something you’re allowed to sell, the market’s psychological anchor loosens. Last week, they truly sold more than 1,600 bitcoins in black and white—and the execution price was even below their cost basis. Even the die-hard longs started cutting and paying rent. It’s no wonder retail traders aren’t calm.
This also made me realize a key point: MicroStrategy’s predicament is precisely because the BTC it holds is “dead assets.” Sitting on 840,000 coins, it can only wait for the price to rise. If cash flow gets tight, selling bitcoin becomes the only option. The stock price then gets chopped along with the coin price. What Trustless Bitcoin Vaults does is to “activate” dead assets—lock BTC in a vault without selling it, use it for staking to earn yield, use it as collateral to borrow stablecoins for turnover. You get cash flow while the BTC still stays in your pocket. Same need for money: one cuts at the bottom, the other lets the coin work.
Of course, collateralized lending carries liquidation risk. If position management isn’t done well, you can still blow up. It’s not like having TBV means you can close your eyes and be fine.
MicroStrategy’s lesson is really just one sentence: hoarding coin faith can’t be used as cash flow. Do you think selling bitcoin by MicroStrategy is perfectly understandable, or do you feel the “faith” has cracked? Leave a comment and let’s talk—this isn’t investment advice. #baby $BABY

That sharp drop during last Wednesday night—BTC dumped seven points in just two hours. A friend in my group decided on the spot to cut his losses and leave. Only after he clicked the redemption did he remember that Babylon’s staked funds can’t be withdrawn until about a week later. He had to watch the market fall for three more days. His coins were stuck in the unbonding period: he couldn’t move them, couldn’t sell them, and couldn’t do anything. That kind of torment is even more painful than losing money itself. Thankfully, this time the market ultimately V-rebounded. He didn’t just avoid a loss—he also dodged panic-driven selling once. But in a different scenario, this is the difference between whether you can actually run or not.
Many people don’t really treat the unbonding period seriously when they stake. They only stare at the APR. But have you thought about it? The BTC you stake is essentially locked. After you request the unbonding, there’s still roughly a week where the coins can’t be transferred and can’t be staked again—they’re completely suspended in midair. In normal times it doesn’t matter much. But in a bull market’s sudden crash, that one week is a life-and-death window. If you want to hedge and run, you can’t. If you want to buy the dip, you can’t—everything has to queue up until time runs out.
So now I advise everyone I meet: @BabylonLabs_io This staking mechanism is designed for long-term positions, not for short-term funds. If you have money you don’t plan to touch for three or five years—dead money—throw it in to earn yield, no problem. After all, you weren’t going to sell anyway. But if you’re thinking about flexible rebalancing, planning to keep capital to buy the dip, or even adding leverage to bet on price swings, please don’t come in. The unbonding period is specifically for harvesting funds like that. In a bull market, the most expensive thing is never the fees. It’s that when you want to move, you can’t.
My own setup is simple: I split my holdings into two parts. The portion I won’t move long-term goes into staking. The portion that trades short-term stays forever in a place where it can be sold with one click. The two don’t interfere with each other. No matter how wild the行情 gets, I won’t move the short-term funds just to chase an extra couple of percentage points in annualized yield.
Are you staking dead money or live money? Let’s discuss in the comments. DYOR#baby $BABY

gate users' money was stolen by 170wu, and now they're denying it. Who would dare to keep money on gate in the future? 🤔

Allox's winning results are out—everyone can check how lucky you are.

Last Monday, a long bearish candle smashed down. In my community, three brothers who were using BTC as collateral to borrow loans woke up to find that the big pie (BTC) was gone. The borrowed USDT (U) was still sitting in their hands, but the pledged BTC was swept away by the liquidation process.
Recently, the TBV native BTC collateralized lending that Babylon and Aave V4 teamed up has gone live on the testnet, and many people are eager to try. I’ll put the ugly truth up front: this trustless vault does eliminate the risk of custodial runaways—your coins are locked on the Bitcoin mainnet and no one holds your private keys—but liquidation risk is still there, none of it disappears. If the collateral ratio falls below the red line, even pre-signed transactions can still be triggered by the liquidator alongside a zero-knowledge proof. The big pie gets swept according to the script rules. No one is malicious the whole time—yet you simply can’t get it back.
To survive extreme market swings, I only recognize three rules. First, don’t max out LTV. If the protocol allows you to borrow 70%, borrow 40% instead. Experienced players work backward from the safety margin using a “halving” discount: if you collateralize BTC worth $100,000 and borrow $30,000, a 65% drop brings you to the brink; if you borrow $60,000 and it drops 40%, you’re done. Any extra buffer is your life.
Second, set your own warning line—don’t wait for the liquidation line. My method is: when the collateral ratio is 10 percentage points away from the red line, I trigger a reminder and start gathering funds; when it’s 5 percentage points away, I repay a portion unconditionally. TBV liquidation is triggered by on-chain proofs. In extreme conditions, network congestion may mean you only have dozens of minutes between receiving the warning and the execution. The wider you set the warning window, the bigger your chance of survival.
Third, always keep some “firefighting” stablecoins outside the vault—at least 15% of your position. When the market dumps, while others sell to top up collateral, you can repay with one click within minutes and pull the collateral ratio back into the safe zone.
Also, two TBV-specific pitfalls to watch out for: liquidation triggering depends on generating zero-knowledge proofs and on-chain confirmations. When market volatility is violent, there can be a time lag—don’t stake your whole position on the network giving you time. One vault can only connect to a single lending protocol. If you want to switch protocols, you have to rebuild the vault and transfer assets. Think about how long you’ll be locked up before you build the position.
TBV is indeed a paradigm-level advancement for BTCFi, but the code doesn’t care—“trustless” means no one can steal your coins, but it also means no one can save your position. Have you tried the testnet experience? How high have you dared to set the collateral ratio? Let’s chat in the comments. DYOR#baby $BABY @BabylonLabs_io

The most expensive lesson in the crypto market was never the loss—it was realizing you couldn’t get out.
Many people join staking projects for the annualized yield, but they don’t notice the lock-up terms. In the market, a large number of PoS projects have unbonding periods of 21 days, 30 days, or even longer. In the last bull run, countless people watched BTC fall in a waterfall from its all-time high, while their staked positions stayed frozen. Their unlock requests were still queued, so they could only watch unrealized gains evaporate. The lock-up period isn’t a fine-print detail—it’s a real liquidity constraint.
Babylon’s unbonding mechanism only requires a two-day buffer. Behind this design are technical reasons: exiting transactions via pre-signed transactions need to wait for confirmation windows on the Bitcoin network to prevent double-spend attacks. Two days is the minimum requirement for the safety mechanism—not an arbitrary lock-up barrier. Compared with competitors that often lock you up for three to four weeks, this gap can mean completely different outcomes in extreme market conditions.
How do you make good use of those two days? The key is to judge in advance, not to apply for unbonding after the price has already collapsed. There are several on-chain signals worth keeping an eye on: the total staked amount across the network drops sharply, token sell-pressure at $BABY noticeably intensifies, and the number of active BTC on-chain addresses in the short term suddenly falls. These are often early signals that “smart money” is starting to retreat. When you see these signals, initiate your unbonding request. Two days later, the coins are in hand, and chances are you’re still at relatively high levels. If you wait until the candlestick chart has already broken through key support before acting, that two-day window turns into extra opportunity cost for missing the move.
Of course, two days isn’t zero. Traders who focus on short-term moves can still get stuck during extreme intraday volatility—there’s no avoiding that. Babylon’s staking mechanism is fundamentally designed for medium- to long-term holders. Holding idle BTC to participate in staking, without relying on that portion of the funds for short-term trading, is the most sensible way to use it.
Liquidity has always been the most easily overlooked—and the most lethal—variable in staking products, especially at critical moments. Going forward, I’ll continue to track the unbonding data of @BabylonLabs_io and the on-chain flow of funds. Do you think the two-day unlock window is enough for the next round of extreme market conditions? Let’s discuss in the comments. #baby

There are currently two more rounds of the spot trading competition that you can participate in. The shopping vouchers given by the event will expire either today or tomorrow—so I’ll use them today first. $EUL $MIRA

To be honest, besides waiting for it to appreciate, BTC in my wallet seems to do nothing else. That’s also why I’ve been researching @BabylonLabs_io recently—I want my sleeping assets to start moving without taking on too much additional risk.
In the past, to make BTC earn yield, you either had to do cross-chain DeFi and worry about the bridge getting hacked, or switch to derivatives and worry about de-pegging. For retail users who just want to hold coins steadily, the options are very limited. Babylon, however, lets BTC directly participate in PoS consensus—you don’t have to turn it into another token, and you don’t have to leave the Bitcoin mainnet security boundary.
It uses Bitcoin’s native scripting capabilities to stake BTC to a PoS chain in exchange for rewards. Without cross-chain bridges or wrapped tokens, your BTC is still your BTC—it just has an added yield feature. This is completely different from converting to receipts and managing them like a financial product. It turns Bitcoin’s security into a rentable resource.
Of course, let me pour some cold water. Babylon is still early-stage, so audits and real-world validation will take time. Staking means liquidity is constrained; you’ll need to read the documentation thoroughly and understand details like unlock periods and slashing penalties—don’t just stare at the APR and ignore the risks.
This isn’t a magic tool for passive income. It’s just an addition to asset allocation thinking. If you’re bullish on BTC long-term and can afford the cost of trial and error, you can give it a try; otherwise, holding normally is more prudent. After all, “not losing more than you could have gained” matters. Whether you should move your coins through Babylon comes down to how you assess your own risk tolerance. #baby $BABY

$ETH This rebound is clearly stronger than $BTC . I don’t know if it will bring about a little fake-market rally 🤔

On a governance proposal submitted by Babylon to Aave, one word made me stop: transfer-restricted (transfer restricted). A token that has its own transfer functionality cut before issuance is something you don’t see very often.
First, let’s talk about the bookkeeping of ordinary wrapped coins. WBTC is essentially an IOU: you hand your BTC to a custodian, and on Ethereum they mint a token worth the equivalent amount for you. Whether it’s valuable or worthless depends entirely on whether the coins in the custodian’s wallet are still there. An IOU only has value if it can circulate—so it must be freely transferable.
Babylon’s vaultBTC has a different origin. After BTC is locked into Trustless Bitcoin Vaults (TBVs), an on-chain vault record is automatically generated. vaultBTC is a 1:1 mapping of that record, created exclusively as collateral for Aave. No one can mint it out of thin air. If you want to redeem the underlying coins, you have to provide a zero-knowledge proof; settlement then goes directly back to an address on Bitcoin.
Only when I line these up could I really taste the difference. WBTC’s issuance power sits with the custodian, while vaultBTC’s generation power is tied to the act of locking itself. WBTC’s credibility comes from a promise, while vaultBTC’s credibility comes from cryptographic conditions. WBTC wants to become money that circulates freely; vaultBTC, on the other hand, doesn’t even want to be money—it just wants to quietly serve as collateral.
But we should also be fair. Transfer restriction is a double-edged sword. Leaving the Aave scenario, it currently has almost no other use. On the liquidation side, you still need WBTC for instant settlement, and the old pipeline hasn’t been fully dismantled yet. So it’s still too early to say Babylon has “killed” wrapped coins.
Therefore, what’s truly new about vaultBTC isn’t that it’s also a kind of voucher, but that the voucher’s meaning is not the same as an IOU for the first time. Both names include BTC: one is an invoice issued by trust, and the other is a receipt stamped by rules. Whether they’re similar or not depends on what they’re backed by. @BabylonLabs_io #baby $BABY

Last week a friend asked me, what exactly is different about @BabylonLabs_io Trustless Bitcoin Vaults from WBTC? I talked for ten minutes about cryptography—he fell asleep. Later I used a house analogy, and he understood in a minute.
WBTC is like transferring ownership of your house to an intermediary. The intermediary gives you a receipt, and then you use that receipt to borrow money elsewhere. The biggest receipt is called WBTC—the one that holds everyone’s house for them—managed by a custody company called BitGo. If one day you want your house back, it depends entirely on whether that intermediary is still around and whether they still follow the rules.
TBV uses a different approach: you take the property deed and use it as collateral. The house never leaves your name for a single day. The vault is a separate UTXO on Bitcoin. When you deposit funds, you pre-sign transactions with the conditions locked in: in any given situation, who is allowed to move what can’t be changed. To withdraw money, you must provide cryptographic proofs. BitVM3 verifies authenticity on Bitcoin. That “intermediary” role is removed completely.
What’s truly valuable in the analogy is the second half. “Trustless” isn’t that nobody is trusted—it means you minimize the part that must be trusted. You can openly verify the math; you can only pray for the intermediary’s character. Babylon never removed trust itself—it removed the *object* of trust.
But of course, the analogy isn’t perfect. With house collateral there are still manual steps like appraisal and registration. TBV also has its own registration venue, and both whitelisted liquidators and oracles still stand at key stages. Trust is reduced, not eliminated—claiming “zero trust” is an overpromise.
So the one-sentence version is: WBTC hands both the house and the keys to someone else; TBV only hands the rules to mathematics. No moving, no handing over keys. The BTC/“big coin” is still yours—you don’t rely on anyone being good, you rely on rules that nobody can change. #baby $BABY

On the @BabylonLabs_io staking page, I saw a line of small text saying that your BTC would be in a slashing/forfeiture (punishable) state—I paused for a few seconds. The words “slashing” and “forfeiture” were enough to scare people off; I’m not the only one it repelled.

Later, once I dug into how the mechanism works, I found out that this line of text is read backwards.

First, figure out who the slashing is meant to target. Proof-of-Stake chains are most afraid of validators signing two blocks at the same height; the chain forks. So every chain keeps a “blade” ready for slashing. The problem is that most protocols write the “blade” too broadly—offline gets penalized, missed signatures get penalized too. Users see the word “slashing” and run.

Babylon’s “blade” is tightly scoped: it triggers only in one situation—when the Finality Provider you selected repeats the signature at the same height. It relies on EOTS signatures: you use it once safely, and the second use automatically exposes the private key. Anyone can then execute the slashing/forfeiture without waiting for anyone’s judgment. The trade-off is that 0.1% of the delegated amount is directly destroyed on Bitcoin, and the FP is permanently removed from the system. Going offline isn’t punished; you just temporarily can’t earn rewards.

Once I understood this, I wasn’t worried anymore. For slashing to be valid, three things must be met: first, a provable double signature; second, the exposed private key comes after; and finally, the Covenant Committee must co-sign. If any one is missing, it can’t be executed. Your own private key is never touched from start to finish, and after slashing, the remaining BTC is returned along the original route.

Compare that to the BABY validator scenario where a double-signing slash is 5%, and Babylon’s 0.1% on BTC is a restrained parameter.

However, staying calm doesn’t mean it’s risk-free. The 0.1% only covers the present. The official documentation states plainly that in the future, as more BSNs are integrated, the slashing conditions may be expanded based on each chain’s needs. The committee co-signing layer is also a trust point. If you truly want to reduce risk, the old reliable method is still to diversify delegations—don’t put all your BTC on a single FP.

So whether that 0.1% is scary or not doesn’t come down to the proportion; it depends on the trigger conditions. People who don’t understand the mechanism are deterred by two words, and the returns go to those who do understand. The “blade” is really meant to prevent malicious actors, not you the staker. #baby $BABY

Where are the coins alpha grabbed today?

$STORJ These project parties are all scrambling to make a quick exit—bear-market is coming.

Yesterday I double-checked the staking data for <0-9>@BabylonLabs_io </0-9> and entered the two figures into a calculator. I pressed through, cleared everything, and re-entered them twice. The vault holds 56,853 BTC locked up; at the current price that’s roughly $3.7 billion. But BABY’s circulating market cap is only a bit over $50 million.

When the market judges how much a project is worth, the usual move is to check the market-cap rankings, then glance at the unlock schedule. The pricing logic is pretty routine. But the staking protocol keeps a second ledger—how much value users actually lock in real assets—and that rarely gets placed side-by-side with market cap for comparison.

I verified the figure of 56,853 from two sources. Babylon’s official dashboard matches third-party TVL statistics. Using today’s BTC price of $64,000, it comes out to about $3.6–$3.7 billion—making it the largest Bitcoin staking protocol locked across the entire network. On the other end, BABY has about 4 billion circulating coins, with a unit price around $0.013. That puts its market cap in the $50 million range. Divide the two and you get a multiple of over 70.

Only after looking at this level did it really hit me: the two ledgers measure fundamentally different things. TVL isn’t recording how much the project is worth; it’s recording how much money people are willing to hand over to these rules. Market cap is recording how much the market is willing to pay for the token’s functionality. One ledger is about security, the other about pricing; between them sits a BTCVaults revenue loop that hasn’t fully run yet.

Of course, a mismatch doesn’t automatically mean an undervaluation. If you switch to FDV, the multiple shrinks to the low 20s. The BTC currently in TVL doesn’t generate revenue for the protocol. Stakers earn inflation rewards—so this ledger isn’t connected to the token’s cash flows. Whether $50 million is expensive or cheap, I can’t draw a conclusion.

So what this set of data truly leaves behind isn’t an answer, but a question. Is the market correctly pricing BABY’s functional value, or is it overlooking the 50,000+ BTC in the vault that will eventually need to be reflected on the same balance sheet? What do you think the market is missing—exactly? #baby $BABY

$BTC 66600 Didn’t pass twice; the pressure at this spot is a bit high. First, let’s look for the downside and see if 61800 can hold, but I feel it won’t. After all, the platform that was finally reached just dropped immediately. The 66600 fake-move multi-task has already been completed

Before the Trustless Bitcoin Vaults whitepaper by Babylon, I carried two questions: what is the collateralization ratio, and where should the alert line be set. After reading it twice, I couldn’t find a parameters table, yet I got stuck on an example. Bob takes 1 BTC and borrows $50,000—if it falls below $50,000, it gets liquidated. The whole paper contains no LTV numbers. I was stunned; maybe I looked at the wrong thing.
In past lending and liquidation, the platform set the parameters. Collateral ratio, liquidation thresholds, and penalties were all written into the contract; the oracle quotes, and when it hits the line it closes the position. Users only watch the health factor. In short, the rules are written by the platform—trust is bundled into it too.
The thinking behind @BabylonLabs_io doesn’t follow this line. The vault is an independent UTXO. When you lock the coins, you pre-sign a batch of Bitcoin transactions, hard-coding the conditions: once you repay, you can redeem; if the market price falls below the agreed threshold, the other party can liquidate. The official calls this a “cryptographic proof of external contract state” that is gated and verified via BitVM3. The liquidation line isn’t a platform parameter; it’s the condition you hard-coded when you signed.
What changed my mind is that there’s basically no platform setting an alert for you here. The safety boundary is fixed at the moment you sign; afterward, you can only monitor prices yourself, adding collateral or repaying in advance. It’s still at the PoC stage, and the VaultBTC experiment market on Morpho only has liquidity of a dozen or so dollars.
The pitfall still has to be laid out. According to the whitepaper, liquidation is triggered by whitelisted liquidators watching the price—it’s not completely permissionless. The whole flow is still hanging on the oracle, so if the oracle quote is wrong, the judgment follows it and goes wrong too. These steps won’t steal your BTC, but they could get you liquidated by mistake.
So I think TBV isn’t really building a borrowing product with better parameters—it’s turning liquidation from a platform rule into cryptographic conditions that you have signed yourself. Will the big pie be forced-liquidated? The answer isn’t in the alert button; it’s in those transactions you signed. Whether you can withstand it with real money is another question.
#baby $BABY

Scrolling through my phone at dawn, I saw yet another new chain announcing that it has integrated Bitcoin security. It reminded me of those chains from three years ago that kept propping up their validators with crazily issued tokens—back then, their token price was already doomed by inflation before it even launched.
Following this announcement, I found the document at @BabylonLabs_io , and suddenly I realized that the “Bitcoin staking” narrative has another side to it: for new chains, it’s effectively a cost-cutting and efficiency-accounting deal.
First, credit where it’s due. The hardest part of a new chain’s cold start is security. If you “self-host” validators, you need to use high-inflation tokens to incentivize them—basically trading token price for security. Babylon lets new chains switch to renting BTC as collateral, paying rewards to Bitcoin stakers instead. That means no need for疯狂增发 tokens, and the value anchor is actually steadier. For users participating in mining on these new chains, reduced sell pressure is indeed a real benefit—and I think this logic holds.
But the reality is that security isn’t a commodity you can buy outright with money. What the new chain buys is verified eligibility. But who gets the authority to set the rules for judging whether stakers violate them? The answer lies in the policy and governance process. If the downstream chain’s governance transparency is insufficient, rules can be changed by a small group of people at any time—then this rented security could become meaningless paper, and miners would face the double risk of both token price and governance rules.
I won’t make any promise that a new chain will be more stable just because it uses BTC collateral, because disclosures of governance details are still a gap—and the gap itself is the risk. Would you pay for a new chain backed by BTC? By the time I finished writing this, the sky was just starting to brighten.
#baby $BABY

Bitcoin beat someone up 😱