FG峰哥论币

Before going to bed last night, I flipped through Babylon’s whitepaper again. The first few chapters were pretty smooth, but when I got to Section 7’s slashing logic—it totally rattled my nerves. The trick of the EOTS automatically leaking the private key is indeed clean and straightforward: double-signed means 100% burns the pledged BTC, and the math is undeniably solid. But the problem is right there, because it doesn’t distinguish whether you were hacked by an attacker, whether a node operator made a slip, or whether network congestion caused a time synchronization offset. Ethereum at least differentiates between minor faults and malicious double-signing, with different penalty strengths, and you can still claw back through community governance. This one is basically hard-coded and welded shut—too absolute. It reminds me of a conversation I had earlier with a friend who works as a market maker. Their biggest concern is exactly this. In one unexpected incident, their own BTC with the Delegators went to zero instantly on the mainnet—risk premium shot through the roof. Even professional custodians had to weigh it carefully; who would dare jump in casually? After TGE, can a governable Slashing threshold be introduced? I think that matters far more than the current math-as-violence approach. Looking at the chart too: May 10, July 10, and August 10—this linear release is basically on-the-label. Monthly fixed dilution is the reality. But on Binance and OKX’s L2 order books, below the integer level, there are ladders of small orders—2% worth—of 50k to 200k in thin, layered steps. It looks more like passive accumulation than something that’s about to be dumped. And around unlock, I haven’t seen continuous large inflows on-chain either. After volatility expands, the close still returns to the midpoint; the probability that market makers are just there to pick up panic orders is higher. What really keeps me from sleeping, though, is TBV’s time-lock setup. Self-custody of the private key and not being cross-chain are definitely亮点, but once those conditions are written into the mainnet script, if it’s not expired, you can’t redeem early. In a bull market, everyone is happy to lock. But what if, in a bear market, there’s a macro-level panic stampede—can the secondary market provide a discounted exit channel for that still-unmatured covenant? That’s probably the real make-or-break line for how far the native staking narrative can go. My thought is very simple now: don’t short naked on the unlock day. Keep placing small orders to buy around the lower end of the midpoint; don’t chase when price runs up along the upper end. Once net inflow turns continuously positive, or on the day TBV’s real fee rate starts flowing back to BABY, then I’ll take a serious look.@babylonlabs_io $BABY #baby

Before going to bed last night, I flipped through Babylon’s whitepaper again. The first few chapters were pretty smooth, but when I got to Section 7’s slashing logic—it totally rattled my nerves.

The trick of the EOTS automatically leaking the private key is indeed clean and straightforward: double-signed means 100% burns the pledged BTC, and the math is undeniably solid. But the problem is right there, because it doesn’t distinguish whether you were hacked by an attacker, whether a node operator made a slip, or whether network congestion caused a time synchronization offset. Ethereum at least differentiates between minor faults and malicious double-signing, with different penalty strengths, and you can still claw back through community governance. This one is basically hard-coded and welded shut—too absolute.

It reminds me of a conversation I had earlier with a friend who works as a market maker. Their biggest concern is exactly this. In one unexpected incident, their own BTC with the Delegators went to zero instantly on the mainnet—risk premium shot through the roof. Even professional custodians had to weigh it carefully; who would dare jump in casually? After TGE, can a governable Slashing threshold be introduced? I think that matters far more than the current math-as-violence approach.

Looking at the chart too: May 10, July 10, and August 10—this linear release is basically on-the-label. Monthly fixed dilution is the reality. But on Binance and OKX’s L2 order books, below the integer level, there are ladders of small orders—2% worth—of 50k to 200k in thin, layered steps. It looks more like passive accumulation than something that’s about to be dumped. And around unlock, I haven’t seen continuous large inflows on-chain either. After volatility expands, the close still returns to the midpoint; the probability that market makers are just there to pick up panic orders is higher.

What really keeps me from sleeping, though, is TBV’s time-lock setup. Self-custody of the private key and not being cross-chain are definitely亮点, but once those conditions are written into the mainnet script, if it’s not expired, you can’t redeem early. In a bull market, everyone is happy to lock. But what if, in a bear market, there’s a macro-level panic stampede—can the secondary market provide a discounted exit channel for that still-unmatured covenant? That’s probably the real make-or-break line for how far the native staking narrative can go.

My thought is very simple now: don’t short naked on the unlock day. Keep placing small orders to buy around the lower end of the midpoint; don’t chase when price runs up along the upper end. Once net inflow turns continuously positive, or on the day TBV’s real fee rate starts flowing back to BABY, then I’ll take a serious look.@BabylonLabs_io $BABY #baby

Missed $MarsCoin , let's see if the $jacket price will speak for itself—it's charging pretty hard too. Will it go to #ALPHA ? Use the Binance wallet.

MarsCoinAlpha

Oh wow, $MarsCoin —its market cap is already over 30 million! The Binance Alpha wealth-creation effect is back again! It’s also produced another batch of on-chain P rookies.

Don’t wait until it gets listed on Binance Alpha before chasing—plan your on-chain layout in advance. When I scan the chain, I use the Binance Wallet—it’s super smooth. Enter my invitation code FFFAAA and you can even save on fees. The P rookies are back!

MarsCoinAlpha

Partly True

After a few months, Binance Alpha is back on meme coins again—$MarsCoin has exploded upwards, and someone else has managed to eat the big meat. Attention is returning to the on-chain space at the right time.

MarsCoinAlpha

$BABY #baby Last night, Old Wang hit me with several back-to-back voice messages. He said he’d basically gone all-in by pledging the entire “big cake” into $BABY, and asked me how the airdrop is actually calculated. I skimmed the documents for a long time, but couldn’t find any clear, definitive numbers—there was just one line: it depends on the effective staking duration and the active level of the Finality Provider. No formula, no multiplier table. It’s completely different from those earlier projects that simply said, “Stake 1,000 to get 500.” Honestly, this path with $BABY is pretty wild. It doesn’t follow the usual project-style rules where the team sets everything in advance and then drops tokens on a schedule. Instead, it writes the incentive logic directly into Bitcoin scripts. From the moment you stake, the outcome is basically set. The time lock, the UTXO state, and the Provider’s on-chain performance all combine to determine how much you can receive. After that, it just comes down to whether the Provider’s uptime is stable enough and whether the proof progress keeps up. In plain terms, the “expected returns” aren’t just promises from the project anymore—they’re verifiable, concrete, on-chain conditions. But on the flip side, the risks become transparent too. The mainnet is still in an early stage—the rewards pool itself isn’t that deep yet, and settlement depends on Babylon submitting state proofs to Bitcoin, so it’s not real-time payout. If the Provider goes offline or something goes wrong, reward settlement gets delayed and the weight could also be reduced. Recently, everyone has been talking about the Aave V4 integration. I think there are two points about TBV that really stand out: no cross-chain bridge, no wrapping Bitcoin. It definitely addresses the custody transfer issue, but the adapter contract becomes a new bottleneck. If the state gets decoupled, the risk shifts from “the custodian runs away” to “the contract logic breaks.” Every BTC-to-EVM cross-ecosystem solution out there currently runs into this structural constraint. In the long run, the adapter’s audit and state-synchronization mechanism matters far more than slogans. @babylonlabs_io Recently, there’s been a run of official announcements about partnerships with Aave, GoMining, and Aegis. The story about native BTC collateral sounds pretty big. But if you look closely, the testnet has indeed run the lending and borrowing flow (in the Signet environment). GoMining is still in the planning stage. And Aegis’s fixed-rate product has to wait until 2026 Q4—its “real value” isn’t on the same level. When you finally get to mainnet launch, the key is whether BTC holders are willing to lock coins for the long term, whether borrowers are willing to bear the costs, and whether the liquidity performance can handle the clearing process.

Verified

$BABY #baby Last night, Old Wang hit me with several back-to-back voice messages. He said he’d basically gone all-in by pledging the entire “big cake” into $BABY , and asked me how the airdrop is actually calculated. I skimmed the documents for a long time, but couldn’t find any clear, definitive numbers—there was just one line: it depends on the effective staking duration and the active level of the Finality Provider. No formula, no multiplier table. It’s completely different from those earlier projects that simply said, “Stake 1,000 to get 500.”

Honestly, this path with $BABY is pretty wild. It doesn’t follow the usual project-style rules where the team sets everything in advance and then drops tokens on a schedule. Instead, it writes the incentive logic directly into Bitcoin scripts. From the moment you stake, the outcome is basically set. The time lock, the UTXO state, and the Provider’s on-chain performance all combine to determine how much you can receive. After that, it just comes down to whether the Provider’s uptime is stable enough and whether the proof progress keeps up. In plain terms, the “expected returns” aren’t just promises from the project anymore—they’re verifiable, concrete, on-chain conditions.

But on the flip side, the risks become transparent too. The mainnet is still in an early stage—the rewards pool itself isn’t that deep yet, and settlement depends on Babylon submitting state proofs to Bitcoin, so it’s not real-time payout. If the Provider goes offline or something goes wrong, reward settlement gets delayed and the weight could also be reduced.

Recently, everyone has been talking about the Aave V4 integration. I think there are two points about TBV that really stand out: no cross-chain bridge, no wrapping Bitcoin. It definitely addresses the custody transfer issue, but the adapter contract becomes a new bottleneck. If the state gets decoupled, the risk shifts from “the custodian runs away” to “the contract logic breaks.” Every BTC-to-EVM cross-ecosystem solution out there currently runs into this structural constraint. In the long run, the adapter’s audit and state-synchronization mechanism matters far more than slogans.

@BabylonLabs_io Recently, there’s been a run of official announcements about partnerships with Aave, GoMining, and Aegis. The story about native BTC collateral sounds pretty big. But if you look closely, the testnet has indeed run the lending and borrowing flow (in the Signet environment). GoMining is still in the planning stage. And Aegis’s fixed-rate product has to wait until 2026 Q4—its “real value” isn’t on the same level. When you finally get to mainnet launch, the key is whether BTC holders are willing to lock coins for the long term, whether borrowers are willing to bear the costs, and whether the liquidity performance can handle the clearing process.

Haven't opened Binance Wallet for a while, and when I dug it out I found over 100 U. I guess the on-chain market has warmed up recently, and the old crew is back to being active. If you need to take part in on-chain interactions—whether it's farming alpha, grabbing rewards, or doing on-chain wealth management—just use Binance Wallet. It’s smooth and seamless. Fill in my invite code to save on trading fees too. Invite code: FFFAAA

You can also copy this address to register for Binance Wallet:
https://web3.binance.com/referral?ref=FFFAAA

BNB-0.34%

ETH-3.10%

Verified

South Korea's stock market has been halted again. What's going on? It feels like they're trying to drag everyone down together. #三星SK海力士杠杆ETF加剧韩国市场波动

SKHYNIX+6.63%

#baby $BABY Yesterday I stayed up late to watch the charts, and I really couldn’t keep my eyes open. I decided to scroll through some posts to take my mind off things—then I ended up stumbling upon BabylonLabs’ TBV, i.e., Trustless Bitcoin Vaults. Just that single trustless core design instantly dispersed my sleepiness. After I dug through the related materials and studied it carefully, I’m genuinely glad I didn’t miss this crucial innovation point. To be honest, Babylon tackles one of the hardest problems in the Bitcoin space: the covenant mechanism in scripting. If you’re familiar with Bitcoin, you know the native scripting language can’t directly control where the funds go after they’re spent. In the past, Bitcoin cross-chain solutions either required trusting a centralized third party, or they relied on multi-sig as a fallback—always with some shortcomings. Babylon, however, breaks the problem cleanly with BitVM3. Most computation is handled off-chain; on-chain it only verifies the compressed fraud proofs. When users withdraw, they must submit a zero-knowledge proof corresponding to the contract state. Only after verification on the Bitcoin main chain does the withdrawal take effect. Throughout the process, all BTC stays locked in the user’s own script and never leaves the Bitcoin network—safety is maxed out. One thing I like most is that each vault is independently isolated: there’s no shared liquidity pool. This is completely different from the pooled model used by mainstream DeFi platforms. In plain terms, it’s a dedicated private safety deposit box. And precisely because of this independently verifiable advantage, protocols like Aave are willing to integrate directly. Users don’t need to wrap anything, don’t need cross-chain, and don’t have to hand over private keys— they can use BTC collateral to borrow stablecoins. The project has also optimized deposit speed and on-chain verification costs. But when it comes to real performance after large-scale deployment, I’m still observing for now. At this stage, TBV is still in the testnet phase: it only integrates with Aave v4. The vaults and addresses have test limits, and all kinds of cooperation plans are still at the blueprint stage. The project’s true strength will have to wait until the mainnet goes live and we can look at core data like actual collateral amounts and borrowing utilization rates. As for the $BABY token, I participated in governance voting before—it gives users who stake a weighted coefficient. It’s more dependable than just holding tokens, because it ties the ecosystem more closely. But for ordinary users, voice and participation are still quite weak. In the long run, token value must ultimately be supported by real use cases: only when TBV’s lending business runs smoothly and protocol fees reliably flow back, can a healthy value system form. @babylonlabs_io

#baby $BABY Yesterday I stayed up late to watch the charts, and I really couldn’t keep my eyes open. I decided to scroll through some posts to take my mind off things—then I ended up stumbling upon BabylonLabs’ TBV, i.e., Trustless Bitcoin Vaults. Just that single trustless core design instantly dispersed my sleepiness. After I dug through the related materials and studied it carefully, I’m genuinely glad I didn’t miss this crucial innovation point.

To be honest, Babylon tackles one of the hardest problems in the Bitcoin space: the covenant mechanism in scripting. If you’re familiar with Bitcoin, you know the native scripting language can’t directly control where the funds go after they’re spent. In the past, Bitcoin cross-chain solutions either required trusting a centralized third party, or they relied on multi-sig as a fallback—always with some shortcomings. Babylon, however, breaks the problem cleanly with BitVM3. Most computation is handled off-chain; on-chain it only verifies the compressed fraud proofs. When users withdraw, they must submit a zero-knowledge proof corresponding to the contract state. Only after verification on the Bitcoin main chain does the withdrawal take effect. Throughout the process, all BTC stays locked in the user’s own script and never leaves the Bitcoin network—safety is maxed out.

One thing I like most is that each vault is independently isolated: there’s no shared liquidity pool. This is completely different from the pooled model used by mainstream DeFi platforms. In plain terms, it’s a dedicated private safety deposit box. And precisely because of this independently verifiable advantage, protocols like Aave are willing to integrate directly. Users don’t need to wrap anything, don’t need cross-chain, and don’t have to hand over private keys— they can use BTC collateral to borrow stablecoins. The project has also optimized deposit speed and on-chain verification costs. But when it comes to real performance after large-scale deployment, I’m still observing for now.

At this stage, TBV is still in the testnet phase: it only integrates with Aave v4. The vaults and addresses have test limits, and all kinds of cooperation plans are still at the blueprint stage. The project’s true strength will have to wait until the mainnet goes live and we can look at core data like actual collateral amounts and borrowing utilization rates. As for the $BABY token, I participated in governance voting before—it gives users who stake a weighted coefficient. It’s more dependable than just holding tokens, because it ties the ecosystem more closely. But for ordinary users, voice and participation are still quite weak. In the long run, token value must ultimately be supported by real use cases: only when TBV’s lending business runs smoothly and protocol fees reliably flow back, can a healthy value system form. @BabylonLabs_io

Bottom-fishing, bottom-fishing! Get on board—$SNDK . The moment has come when others are afraid and I’m greedy.

SNDK+0.33%

Partly True

US stocks tonight will be a sea of blood; the KOLs who previously urged people to go long are coming out now—go take two steps, then. #SK海力士跌13%韩股KOSPI跌10%

EWY+2.01%

SKHYNIX+6.63%

$BABY For this period of time, I’ve calmed down and focused on research @babylonlabs_io , and found that there are quite a few common misconceptions in the community. Let me briefly share my genuine take. Many people see that the on-chain BTC being locked in custody is huge in volume, and then naturally become bullish on $BABY. However, this line of reasoning isn’t rigorous. First, we need to clarify the most easily confused risk rules: the network has two independent capital systems. BTC custody delegates work to FP and the final execution/punishment is handled there, where violations lead to forfeiture at 0.1%; $BABY is staked to consensus validators, and the double-sign slashing is 5%. Their responsibilities and trigger conditions are completely different. Comparing just the numbers is meaningless. Also, a node going offline doesn’t equal a double-sign event—it won’t directly result in BTC being penalized. This is something many explainer articles get wrong. Looking through the FP operations/maintenance documentation, you can also see the trade-offs in the design. After FP keys are generated, they can’t be changed arbitrarily, which ensures the node identity is traceable and leaves no room for secretly swapping keys—but it also raises the operational/maintenance threshold. If there’s a risk of key leakage, you can’t simply rotate and patch it directly; you can only rebuild the node and guide users to migrate their delegations. Going forward, when everyone selects an FP, you shouldn’t only look at uptime and commission. Operational isolation measures and key-protection contingency plans also need to be factored in. As for the fundamental issue everyone cares about most: the large amount of BTC that’s staked cannot generate cash flow that back-fills $BABY holders. At this stage, staking rewards come from token inflation. BTC holders exchange BTC safety guarantees, while $BABY holders receive inflation returns. These two reward channels are independent of each other. Combined with the ongoing unlocking of shares and annual inflation, the circulating supply keeps expanding. The BSN buyback-and-burn concept is quite appealing, but the actual realized benefits haven’t been delivered yet. Until newly staked BTC can consistently be converted into token-capture returns, a high TVL mostly just reflects the infrastructure scale of the BTC ecosystem. So I think Babylon’s BTC security narrative has long-term value, but the infrastructure value and token valuation should be viewed separately. The narrative hasn’t been disproven yet, but to achieve a valuation switch, we still need to wait for real income and on-chain burn data to materialize. #baby

$BABY For this period of time, I’ve calmed down and focused on research @BabylonLabs_io , and found that there are quite a few common misconceptions in the community. Let me briefly share my genuine take.

Many people see that the on-chain BTC being locked in custody is huge in volume, and then naturally become bullish on $BABY . However, this line of reasoning isn’t rigorous. First, we need to clarify the most easily confused risk rules: the network has two independent capital systems. BTC custody delegates work to FP and the final execution/punishment is handled there, where violations lead to forfeiture at 0.1%; $BABY is staked to consensus validators, and the double-sign slashing is 5%. Their responsibilities and trigger conditions are completely different. Comparing just the numbers is meaningless. Also, a node going offline doesn’t equal a double-sign event—it won’t directly result in BTC being penalized. This is something many explainer articles get wrong.

Looking through the FP operations/maintenance documentation, you can also see the trade-offs in the design. After FP keys are generated, they can’t be changed arbitrarily, which ensures the node identity is traceable and leaves no room for secretly swapping keys—but it also raises the operational/maintenance threshold. If there’s a risk of key leakage, you can’t simply rotate and patch it directly; you can only rebuild the node and guide users to migrate their delegations. Going forward, when everyone selects an FP, you shouldn’t only look at uptime and commission. Operational isolation measures and key-protection contingency plans also need to be factored in.

As for the fundamental issue everyone cares about most: the large amount of BTC that’s staked cannot generate cash flow that back-fills $BABY holders. At this stage, staking rewards come from token inflation. BTC holders exchange BTC safety guarantees, while $BABY holders receive inflation returns. These two reward channels are independent of each other. Combined with the ongoing unlocking of shares and annual inflation, the circulating supply keeps expanding.

The BSN buyback-and-burn concept is quite appealing, but the actual realized benefits haven’t been delivered yet. Until newly staked BTC can consistently be converted into token-capture returns, a high TVL mostly just reflects the infrastructure scale of the BTC ecosystem.

So I think Babylon’s BTC security narrative has long-term value, but the infrastructure value and token valuation should be viewed separately. The narrative hasn’t been disproven yet, but to achieve a valuation switch, we still need to wait for real income and on-chain burn data to materialize. #baby

Verified

Korean stock market plunges—today global investment markets are in trouble again. MD, do you still have storage? Do you still have SK hynix? Do you still have Samsung? Do you still have Micron? $MU
#美国存储股扩大跌幅 #韩国KOSPI转跌芯片股拖累

MUonAlpha

MU+0.14%

Re-read the Babylon staking contract documentation of @babylonlabs_io , and a detail kept me stuck for a long time. Turns out the entire staking process isn’t executed dynamically—it’s a transaction map drawn in advance. The protocol pre-signs all the relevant transactions for you at the time you stake, including the unbonding and slashing paths. The flow of funds is already fixed on the board before the UTXO is actually locked. I remember thinking: why not just use a dynamic contract? Then it clicked—Bitcoin Script’s limited expressiveness simply can’t handle the stateful logic Babylon needs. So it uses a pre-signed transaction map to emulate contract behavior: the staked UTXO has only three possible routes. When the time lock expires, you can retrieve it yourself; you can unbond early in coordination with the committee; or it can be slashed when a validator’s double signature is verified. The core advantage of this design is that even if the Babylon chain goes down, the predefined paths on the Bitcoin mainnet can still be executed, with fund safety tightly pinned to the native UTXO rules. But the trade-off is obvious too: flexibility is nearly zero. Want to change configurations? No—unbond first, then stake again. I couldn’t figure it out before—since Bitcoin has no smart contracts, how can Babylon automatically slash? After re-reading the whitepaper, I understood: it follows an extreme cryptographic route, using Extractable One-Time Signatures (EOTS). If validators behave honestly, they only need to sign once with a private key. But once they co-sign at the same height, the signature itself leaks the private key. Anyone who obtains the private key can broadcast a destruction transaction on the Bitcoin chain, burning the slashing target’s staked assets. This isn’t about determining evidence on-chain; it’s about making malicious behavior automatically expose the cryptographic proof. Compared with schemes that strongly bridge Bitcoin to external networks and rely on multisig, Babylon is notably restrained. It doesn’t try to rewrite Bitcoin’s underlying layer—instead, it fully leverages Taproot scripts, locking each piece of funds independently into native state units, thereby avoiding the risks of shared liquidity pools from the ground up. Of course, it isn’t perfect. The script conditions are too complex, demanding extremely high engineering capability from the development team. Mainnet throughput also introduces friction in interactions. But it lays out the choice clearly: when earning on-chain yield on Bitcoin, do you want convenience with a potential black-box intermediary, or a heavier—but tamper-proof—cryptographic wall? I choose the latter. That kind of determinism is what truly gives Bitcoin staking its confidence. $BABY #baby

Re-read the Babylon staking contract documentation of @BabylonLabs_io , and a detail kept me stuck for a long time.

Turns out the entire staking process isn’t executed dynamically—it’s a transaction map drawn in advance. The protocol pre-signs all the relevant transactions for you at the time you stake, including the unbonding and slashing paths. The flow of funds is already fixed on the board before the UTXO is actually locked.

I remember thinking: why not just use a dynamic contract? Then it clicked—Bitcoin Script’s limited expressiveness simply can’t handle the stateful logic Babylon needs. So it uses a pre-signed transaction map to emulate contract behavior: the staked UTXO has only three possible routes. When the time lock expires, you can retrieve it yourself; you can unbond early in coordination with the committee; or it can be slashed when a validator’s double signature is verified.

The core advantage of this design is that even if the Babylon chain goes down, the predefined paths on the Bitcoin mainnet can still be executed, with fund safety tightly pinned to the native UTXO rules. But the trade-off is obvious too: flexibility is nearly zero. Want to change configurations? No—unbond first, then stake again.

I couldn’t figure it out before—since Bitcoin has no smart contracts, how can Babylon automatically slash? After re-reading the whitepaper, I understood: it follows an extreme cryptographic route, using Extractable One-Time Signatures (EOTS). If validators behave honestly, they only need to sign once with a private key. But once they co-sign at the same height, the signature itself leaks the private key. Anyone who obtains the private key can broadcast a destruction transaction on the Bitcoin chain, burning the slashing target’s staked assets. This isn’t about determining evidence on-chain; it’s about making malicious behavior automatically expose the cryptographic proof. Compared with schemes that strongly bridge Bitcoin to external networks and rely on multisig, Babylon is notably restrained. It doesn’t try to rewrite Bitcoin’s underlying layer—instead, it fully leverages Taproot scripts, locking each piece of funds independently into native state units, thereby avoiding the risks of shared liquidity pools from the ground up.

Of course, it isn’t perfect. The script conditions are too complex, demanding extremely high engineering capability from the development team. Mainnet throughput also introduces friction in interactions. But it lays out the choice clearly: when earning on-chain yield on Bitcoin, do you want convenience with a potential black-box intermediary, or a heavier—but tamper-proof—cryptographic wall? I choose the latter. That kind of determinism is what truly gives Bitcoin staking its confidence. $BABY #baby

Before I saw the BTCFi project $BABY , my first reaction was: not again—we have to do cross-chain, wrap assets, and find a third-party custodian. As someone who has kept coins in a cold wallet for years without touching them, I really don’t dare to get involved; the trust cost is too high. But after reading the official documentation of @babylonlabs_io , I realized I was being too narrow-minded. It keeps BTC locked on the Bitcoin mainnet, uses Taproot scripts to control it, and on the Ethereum side it only records a single state—both sides are atomically bound. Redemption is verified through the BABE challenge mechanism. There’s no cross-chain bridge for the whole process. You don’t need Wrapped BTC, and there’s no centralized custodian. In plain terms, you’re not trusting some team or institution—you’re trusting the cryptography and the protocol itself. This is what BTCFi should look like. It’s not about making a product; it’s about building base infrastructure for native BTC. Lending is just the first step; later, on-chain applications around BTC can grow on top of this. That said, it’s still in the testing stage. I’m mainly watching three metrics: mainnet TVL growth, the number of DeFi protocols integrated, and the real redemption success rate. Only if these data continue trending well can it truly show that it lowers the barrier for BTC to participate in DeFi. Recently I’ve also been keeping an eye on the $BABY token unlocks. According to the Tokenomics, this month insiders unlock about 136 million, ecosystem and R&D release 112.5 million, and with monthly inflation, the new supply is roughly 294 million tokens. But don’t panic—unlocking doesn’t necessarily mean a sell-off. Investors may continue holding or staking; the ecosystem side has to pay costs, and stakers make different choices after receiving rewards. The key is to look at the actual sell pressure multiplied by the sell ratio, and compare it to the order book’s ability to absorb demand. I’m more optimistic about their plan to put the tokens into ecosystem development, R&D, and network security. If these investments can bring more real BTC-related business and revenue, the added supply could very well be absorbed by growing purchasing power. At the end of the day, if native BTC can truly and safely participate in DeFi in an efficient way, who would want to use those wrapping solutions? The Babylon path is definitely worth continuing to watch. #baby

Before I saw the BTCFi project $BABY , my first reaction was: not again—we have to do cross-chain, wrap assets, and find a third-party custodian. As someone who has kept coins in a cold wallet for years without touching them, I really don’t dare to get involved; the trust cost is too high.

But after reading the official documentation of @BabylonLabs_io , I realized I was being too narrow-minded. It keeps BTC locked on the Bitcoin mainnet, uses Taproot scripts to control it, and on the Ethereum side it only records a single state—both sides are atomically bound. Redemption is verified through the BABE challenge mechanism. There’s no cross-chain bridge for the whole process. You don’t need Wrapped BTC, and there’s no centralized custodian.

In plain terms, you’re not trusting some team or institution—you’re trusting the cryptography and the protocol itself. This is what BTCFi should look like. It’s not about making a product; it’s about building base infrastructure for native BTC. Lending is just the first step; later, on-chain applications around BTC can grow on top of this.

That said, it’s still in the testing stage. I’m mainly watching three metrics: mainnet TVL growth, the number of DeFi protocols integrated, and the real redemption success rate. Only if these data continue trending well can it truly show that it lowers the barrier for BTC to participate in DeFi.

Recently I’ve also been keeping an eye on the $BABY token unlocks. According to the Tokenomics, this month insiders unlock about 136 million, ecosystem and R&D release 112.5 million, and with monthly inflation, the new supply is roughly 294 million tokens. But don’t panic—unlocking doesn’t necessarily mean a sell-off. Investors may continue holding or staking; the ecosystem side has to pay costs, and stakers make different choices after receiving rewards. The key is to look at the actual sell pressure multiplied by the sell ratio, and compare it to the order book’s ability to absorb demand.

I’m more optimistic about their plan to put the tokens into ecosystem development, R&D, and network security. If these investments can bring more real BTC-related business and revenue, the added supply could very well be absorbed by growing purchasing power.

At the end of the day, if native BTC can truly and safely participate in DeFi in an efficient way, who would want to use those wrapping solutions? The Babylon path is definitely worth continuing to watch. #baby

#baby $BABY to be honest, when I just saw the @babylonlabs_io project, I thought, isn’t this just staking with a different outfit? Lock BTC to earn yield—same old playbook. But after reading the docs for two days, it turned out to be completely different. In plain terms, BTC staking is putting up collateral: you lock your Bitcoin on-chain by delegating it to validator nodes. If they maintain the network properly, you get rewards; if they act maliciously, they get fined. The key question it addresses is: who covers the security guarantees. TBV took a different direction. It’s like an intelligent insurance safe with rules hard-coded in place. Each safe corresponds to a specific BTC UTXO. Funds are isolated, and you can’t reuse the same collateral for multiple positions. When other DeFi protocols see clearly that your BTC is locked transparently and that the validator status is verifiable, they dare to lend you other assets. This is what actually unlocks Bitcoin’s liquidity—while Bitcoin never leaves its native chain. One side earns money for taking on the security responsibility; the other side gets borrowing capacity. Interest, volatility, and liquidation risks are all on you. Don’t get distracted by talk of “double earnings.” Research it all you want—at the moment, TBV is still running on the testnet. While digging through the BABY docs, I found that it uses CometBFT for consensus—basically combining the Cosmos setup with Bitcoin staking. With 100 validators producing blocks, and 60 stakers signing off on finality, the design is pretty clever. But the word “translation” in the TBV docs moved me more. At its core, it’s translating: converting the logic of DeFi contracts into something the Bitcoin chain can understand. Bitcoin scripts can’t natively read other-chain logic—that’s the real hard part. The team is working with the BitVM Alliance. The latest progress is submitting a proposal to the Aave DAO, aiming to plug TBV into Aave V4, with two newly designed Spoke contracts specifically for borrowing assets and liquidation. When the Vault is created, the rules are written in stone; after that, nobody can tamper with them. Trust is delegated to the code itself. So what’s truly worth thinking about with $BABY isn’t just an extra layer of yield—it’s whether Bitcoin can take on more roles in the DeFi world through rules alone, without wrapping or custody. If they can get this to work, the imagination space is enormous.

#baby $BABY to be honest, when I just saw the @BabylonLabs_io project, I thought, isn’t this just staking with a different outfit? Lock BTC to earn yield—same old playbook. But after reading the docs for two days, it turned out to be completely different.

In plain terms, BTC staking is putting up collateral: you lock your Bitcoin on-chain by delegating it to validator nodes. If they maintain the network properly, you get rewards; if they act maliciously, they get fined. The key question it addresses is: who covers the security guarantees.

TBV took a different direction. It’s like an intelligent insurance safe with rules hard-coded in place. Each safe corresponds to a specific BTC UTXO. Funds are isolated, and you can’t reuse the same collateral for multiple positions. When other DeFi protocols see clearly that your BTC is locked transparently and that the validator status is verifiable, they dare to lend you other assets. This is what actually unlocks Bitcoin’s liquidity—while Bitcoin never leaves its native chain.

One side earns money for taking on the security responsibility; the other side gets borrowing capacity. Interest, volatility, and liquidation risks are all on you. Don’t get distracted by talk of “double earnings.” Research it all you want—at the moment, TBV is still running on the testnet.

While digging through the BABY docs, I found that it uses CometBFT for consensus—basically combining the Cosmos setup with Bitcoin staking. With 100 validators producing blocks, and 60 stakers signing off on finality, the design is pretty clever. But the word “translation” in the TBV docs moved me more. At its core, it’s translating: converting the logic of DeFi contracts into something the Bitcoin chain can understand. Bitcoin scripts can’t natively read other-chain logic—that’s the real hard part.

The team is working with the BitVM Alliance. The latest progress is submitting a proposal to the Aave DAO, aiming to plug TBV into Aave V4, with two newly designed Spoke contracts specifically for borrowing assets and liquidation. When the Vault is created, the rules are written in stone; after that, nobody can tamper with them. Trust is delegated to the code itself.

So what’s truly worth thinking about with $BABY isn’t just an extra layer of yield—it’s whether Bitcoin can take on more roles in the DeFi world through rules alone, without wrapping or custody. If they can get this to work, the imagination space is enormous.

#baby $BABY To be honest, I’ve always been a bit immune to projects in the BTC ecosystem. No matter how you flip it, it keeps coming back to the same three moves: wrapping, cross-chain, and staking. But @BabylonLabs_io really made me look twice.

Not because it’s that amazing, but because its way of thinking is a bit different from everyone else’s. Others are all trying to figure out how to move BTC out of the Bitcoin network. It’s thinking about letting BTC stay at home—while still going out to work and make money.

The core is two things: one is native staking, similar to posting collateral margin to provide security endorsement for other chains; the other is TBV (Trustless Bitcoin Vaults), which is basically putting a smart lock on BTC. The coins stay in your own wallet, but DeFi can recognize this “lock” and treat it as collateral. Put simply, it enables BTC to be used across multiple scenarios without leaving home. No wrapping. No crossing-chain bridges. The security is genuinely a notch higher.

But don’t get too excited yet. TBV is still on the testnet for now, and the official team admits that in the early stage it hasn’t been integrated with the staking system. The so-called “staking while collateralizing” is still at the PPT stage. The consensus mechanism uses dual verification—sounds hardcore, but in real operation the coordination cost isn’t low. As soon as either side’s validators underperform, the whole chain can get stuck.

Overall, I agree with BABY’s direction, but the rollout pace is a bit slow. As a governance token, whether $BABY can truly support this whole system later on will largely depend on when TBV can run smoothly in real life. If there’s any progress, I’ll dig in again afterward.

Trade with the Binance Wallet and win the 60,000 USDG prize pool!

The Binance Wallet now supports Robinhood!

Season 4 On-Chain Trading Experience Contest is live—come to the Binance Wallet and check in for Robinhood to win the 60,000 USDG prize pool.

How it works:
The game uses tokens issued by Virtuals Protocol on the Robinhood chain. Prizes are distributed based on realized P/L rankings. The top 100 will share the prize pool, and the winner can receive 12,000 USDG.

Participation requirements:
1》Register and trade using the Binance Wallet (no private keys)
2》Only Virtuals Protocol tokens issued on the Robinhood chain are counted
3》Trading pairs must include $VIRTUALS, $USDG, and $ETH or $WETH
4》To be eligible for the ranking, you must complete at least 1 buy and 1 sell
5》Your wallet cannot export private keys, and you cannot use the same wallet to trade on other platforms

The activity has started and ends on August 5.
You need to sign up first. If you’re already playing Robinhood, you can join along—while trading to make profits, you can also get an additional reward.

Binance Wallet exclusive link:
https://web3.binance.com/pnl-tc/szn4?ref=FFFAAA

ETH-3.10%

VIRTUAL-3.35%

$BABY The Bitcoin ecosystem has been really lively lately, but after looking around for a full cycle, Babylon Labs is the one worth keeping an eye on. In the past, we held BTC in our hands. Besides hoarding and waiting for the price to rise, there wasn’t much we could do. If you wanted to get involved in DeFi, you either had to do cross-chain wrapping—which comes with frightening risks—or hand it over to a centralized platform, spending your days worrying about rug pulls. But Babylon offers a new approach: it lets us stake native BTC. Your assets don’t need to move, and you don’t have to trust any third party—the security is as solid as it gets. @babylonlabs_io What’s so smart about it? It takes Bitcoin’s powerful consensus and security capabilities and exports them to other PoS chains. In plain terms, BTC is no longer just “dead money.” It becomes the security foundation for the entire on-chain ecosystem. What’s even more impressive is the Trustless Bitcoin Vaults (TBV) it recently worked on—somehow it can let native BTC use cryptographic proofs to become collateral in Ethereum DeFi, with self-custody and liquidity all taken care of. If this works out, lending, stablecoins, and derivatives could all get pulled into the fold—and I can hardly even imagine the possibilities. Also, the $BABY token doesn’t feel like a trap: besides fees and governance, it enables deep participation in the ecosystem. The team has set a pretty long unlock schedule, so near-term sell pressure is low—which is a big plus in this bear market environment. Of course, TBV is still in testnet. Whether liquidation is solid, and whether cross-chain verification is trustworthy, we’ll need to watch. But the narrative of BTC security + staking + PoS already has incredible upside. Bitcoin is evolving from a savings vault into a productive asset—and Babylon is targeting exactly that lifeline. I’ll be actively monitoring and backing this project. If there are any updates, I’ll report back to the brothers. #baby

$BABY The Bitcoin ecosystem has been really lively lately, but after looking around for a full cycle, Babylon Labs is the one worth keeping an eye on.

In the past, we held BTC in our hands. Besides hoarding and waiting for the price to rise, there wasn’t much we could do. If you wanted to get involved in DeFi, you either had to do cross-chain wrapping—which comes with frightening risks—or hand it over to a centralized platform, spending your days worrying about rug pulls. But Babylon offers a new approach: it lets us stake native BTC. Your assets don’t need to move, and you don’t have to trust any third party—the security is as solid as it gets.

@BabylonLabs_io What’s so smart about it? It takes Bitcoin’s powerful consensus and security capabilities and exports them to other PoS chains. In plain terms, BTC is no longer just “dead money.” It becomes the security foundation for the entire on-chain ecosystem. What’s even more impressive is the Trustless Bitcoin Vaults (TBV) it recently worked on—somehow it can let native BTC use cryptographic proofs to become collateral in Ethereum DeFi, with self-custody and liquidity all taken care of. If this works out, lending, stablecoins, and derivatives could all get pulled into the fold—and I can hardly even imagine the possibilities. Also, the $BABY token doesn’t feel like a trap: besides fees and governance, it enables deep participation in the ecosystem. The team has set a pretty long unlock schedule, so near-term sell pressure is low—which is a big plus in this bear market environment.

Of course, TBV is still in testnet. Whether liquidation is solid, and whether cross-chain verification is trustworthy, we’ll need to watch. But the narrative of BTC security + staking + PoS already has incredible upside. Bitcoin is evolving from a savings vault into a productive asset—and Babylon is targeting exactly that lifeline. I’ll be actively monitoring and backing this project. If there are any updates, I’ll report back to the brothers. #baby

Disputed

@grvt_io 7 May 30 TGE. I didn’t participate in the coin-flipping/loot-streaming before, so I don’t know whether there’s a wealth-creation effect. I miss the old air-drop effect—especially now during the bear market. Let’s have a few wealth-creation effects to boost everyone’s morale. I didn’t farm it, but seeing someone farmed into big money is still good.