jojo橘子

Every order you get a few cuts and you run. You don’t take hits—you fold when the direction is wrong. Let me try this kind of style—will it work? Every day is losing money. I’m really losing too much! Every time it’s loss, it’s because I take the position and hold it through the drawdown. Today I’ll try doing a Sandisk (SNDY) wave/interval trade—will I make money or lose? The news flow today also feels okay, and the geopolitical issues have eased a bit. We’ll just see how things go when the US stock market opens tonight. #TradFi晒单

I saw Hindenrank give Babylon a C- risk rating of 57/100. A lot of people see C- and swipe past, thinking it’s FUD. But if you look closely at the rating notes—category leader status + novel cryptography + covenant trust + cascade risk to LRTs—this places it in high-variance territory.

Translate it like this: track leader + new cryptography + covenant trust + cascading risk to LRTs = high variance. @BabylonLabs_io

What does it mean? Babylon is currently the largest protocol in the BTC staking track, with TVL of $5.6 billion. But “largest” and “safest” are two different things. In April 2026, the vulnerability incident involving KelpDAO already demonstrated how terrifying the cascade risk of LRT bridging can be—if one link goes wrong, the entire nested structure suffers.

What’s even more concerning is another set of data: a single un-staking event withdrew 32% of TVL, about $1.26 billion. What does that imply? The “big whales” are highly concentrated—just a few large stakers can shake the whole protocol.

I’m not saying Babylon will fail. I’m saying that when a protocol has all three labels—(1) the track’s biggest cryptographic innovation and (2) whale concentration—you should at least know what kind of ground you’re standing on. C- isn’t a verdict; it’s a medical checkup report. Read it—skip it at your own risk. #baby $BABY

While I was looking through the Babylon data dashboard, one number kept catching my attention for a long time: TVL of $5.6 billion, and a token market cap of just a little over $50 million. The ratio is close to 100:1.

What does that mean in the DeFi space? Aave’s TVL is less than half of Babylon’s, but its token market cap is more than a dozen times that of Babylon. It’s not that Babylon is “too cheap”; it’s that the market simply isn’t pricing BABY as a value-capture tool. @BabylonLabs_io

But I think the real issue lies somewhere else. Babylon’s core business generates protocol revenue by enabling BTC holders to stake and earn yield without moving their coins or bridging cross-chain. As of now, this revenue doesn’t seem to be getting directed toward the BABY token. Gas fees don’t need to be paid in BABY, governance rights are still in an early stage, and the extra 2.35% inflation rewards from liquid/staking are more like a lock-in incentive than a distribution of value. In other words, Babylon has built one of the toughest BTCFi infrastructures in the entire industry—but BABY’s role within that infrastructure is currently more like an access pass for the experience rather than a claim on dividends.

a16z valued it at $800 million when they invested, but its current market cap is $50 million—down 93%. You can say the market is wrong, or that the valuation model changed. But from the perspective of value captured by the protocol, BABY has not delivered the “answer” yet.

I’ll keep watching one thread: after TBV and Aave V4 officially launch, how protocol fees will actually be allocated.
If BABY is always positioned only for governance plus inflation rewards, then this $50 million market cap might not even be the bottom.

When you choose a high-quality token, what do you think you should look at most? Feel free to interact—I'll keep writing quality posts from time to time to serve everyone! #baby $BABY

I've been thinking about how Babylon's timestamp protocol actually works. It takes data such as the PoS chain's block checkpoints and fraud proofs, and writes them into Bitcoin blocks through a relay mechanism. Once this data is on the Bitcoin chain, it becomes immutable—everyone knows the cost of changing a Bitcoin transaction.

Babylon designed a three-layer architecture. The bottom layer is the Bitcoin network, which provides an immutable timestamping service. The middle layer is Babylon itself, responsible for packaging PoS chain events into checkpoints and batching them for submission to Bitcoin. The top layer consists of the connected PoS chains, i.e., BSN.@BabylonLabs_io

To control the frequency of checkpoints, Babylon implemented an epoch mechanism: every M consecutive Babylon blocks form an epoch, and a checkpoint is created only at epoch boundaries. The benefit of this approach is reduced Bitcoin transaction fee overhead; the downside is that checkpoints are delayed. If a security issue occurs on a PoS chain in the middle of an epoch, it must wait until the next boundary before it can be anchored to Bitcoin. This delay window is the time gap an attacker can exploit.

The timestamp protocol also plays a key role in preventing long-range attacks. One of the most feared attacks on a PoS chain is for an attacker to rewrite the entire chain history starting from the genesis block. But if every critical state of the chain has a timestamp record on Bitcoin, the attacker can't tamper with history without exposing themselves. Babylon also writes its own validator set changes to Bitcoin via checkpoints, which is effectively an extra safety measure for its consensus layer.

In terms of design logic, everything is consistent. But the problem is that parameters such as checkpoint frequency, batch size, and how fees are allocated are currently fixed at the protocol level. If the Bitcoin network becomes congested and checkpoint transactions get stuck in the mempool and can't be confirmed, the PoS chain's security guarantees will be weakened.#baby $BABY

I carefully reviewed Babylon’s confiscation mechanism documentation during this period and found a core detail that’s very easy to overlook: the platform sets two confiscation rules with drastically different penalties for BTC staking versus BABY staking.

At the finality node, if there is equivocation—meaning the node signs two different messages at the same block height—it will only be penalized by confiscating 0.1% of the staked BTC. Looking at this ratio alone, it seems quite low: staking one BTC would only result in a deduction of one per mille, and the confiscated BTC is sent directly to a black hole address for permanent destruction. More importantly, the violating finality node will have its confiscation status permanently locked, and going forward it can never again obtain any BTC staking rewards; over the long term, the hidden losses are actually significant.@BabylonLabs_io

However, for BABY stakers, the confiscation ratio is directly 5%, which is a full fifty times higher than the BTC confiscation ratio. I’ve thought repeatedly about the logic behind this differentiated design. Most likely, it’s because the BABY token has stronger liquidity and is more flexible in circulation, so an excessively low penalty would not provide effective deterrence. And since BTC’s value is huge in magnitude, setting the confiscation ratio too high would strongly discourage staking users, which would be detrimental to the overall ecosystem’s growth in staked volume.

The underlying logic of this mechanism is actually understandable, but I found a highly unreasonable imbalance. The risk borne by BABY stakers is fifty times higher than that of BTC stakers, yet the official whitepaper completely fails to clearly state whether governance rights are aligned with the risk level for the two. The rule definitions in this area are very vague.

In addition, I also noticed that Babylon’s confiscation trigger conditions are generally too lenient. Simply having a node go down and miss a vote, or various kinds of non-double-signing ordinary mistakes, will not trigger confiscation penalties. In other words, as long as the node does not actively violate by double-signing, even if it frequently goes offline, it won’t have any coins deducted. Only the node going offline reduces on-chain participation, directly lowering staking returns, which is effectively an indirect loss of user收益.#baby $BABY

I’m also fed up with Korean stocks. They keep falling every day—whatever I buy keeps dropping. It feels more stimulating than mainstream crypto—up and down dozens of points in a day, back and forth like needles. My little heart really can’t take it anymore!
I think I’ll just stock up a bit on spot index products instead. At least I don’t have to worry about it not coming back!
#TradFi晒单

When staking BTC, I kept thinking about a crucial question: after staking, who exactly ends up holding your Bitcoin? After reviewing Babylon’s entire mechanism, the answer is clear—no one truly takes your coins away.

It doesn’t go through a cross-chain bridge, doesn’t require wrapping BTC into WBTC, and you don’t need to transfer your BTC to any custodial institution. Your Bitcoin always remains stored in the UTXOs of the Bitcoin mainnet, and you retain control of the private keys throughout. The entire remote staking process runs on cryptography and Bitcoin’s scripting language. The technical logic is solid and hardcore, but objectively speaking, for ordinary investors, it’s not easy to fully grasp these principles—the threshold is fairly high.

If you carefully read the @BabylonLabs_io whitepaper, you’ll find that Babylon’s real goal isn’t merely to make BTC generate yield. Instead, it aims to export Bitcoin’s powerful economic security capabilities to major PoS chains. So far, more than 56,000 BTC are participating in staking, with a value of about $5.6 billion.

What does that mean?

It means BTC no longer has to just sit in your wallet, preserving value quietly. Without moving assets, you can rely on it to provide security support for other blockchains and also receive BABY as a reward. At first glance, the advantages look substantial, but returns always come with security constraints. The protocol includes a slashing/penalty mechanism: if malicious behavior occurs, the staked portion of BTC will be deducted. As long as we ourselves don’t violate any rules, there’s no need to worry about risk—the main hidden danger comes from the validator you delegate to.

Choosing a node is not something to take lightly. If the delegated validator causes harm or incidents, we will also bear the corresponding financial losses. If you want to participate in Babylon staking, you can’t just focus on the returns—make sure you understand the risk points in advance, such as node selection and slashing rules. #baby $BABY

Before I figured out Babylon’s PoS and Timestampping protocol, I always thought it was just some tricks added to Bitcoin scripting to make it seem more useful. The whitepaper is packed with complex cryptographic primitives and synchronization logic, and it never really explains how it improves transaction speed.

I paused and realized maybe I’d taken the wrong direction.

In the past, when we talked about cross-chain or sidechains, the core goal was speed and compatibility. Either wrap BTC and move it over, or build a high-performance chain that claims to be secure. In plain terms, everyone wants to unlock Bitcoin’s liquidity, and the trust rests on multisig or the bet that a new chain’s consensus will hold.

The idea behind @BabylonLabs_io isn’t on that track. Through a timestamping protocol, the PoS chain continuously writes its block hashes and validator signatures onto Bitcoin. This isn’t seeking liquidity—it’s seeking absolute historical finality. The whitepaper calls this external alignment of security. A PoS chain can be fast and handle high concurrency, but its finality is ultimately confirmed by Bitcoin’s slow blocks.

What changed my mind is that this mechanism solves PoS’s most fatal long-range attack and the unbonding-period problem. Once the state is anchored into a Bitcoin script, no attacker can rewrite that history unless they attack Bitcoin itself. A unbonding period that used to last weeks can, thanks to confirmation by the world’s safest ledger, be safely shortened to just a few hours.

But there’s a catch. As the whitepaper puts it, this kind of security also has a cost. If the BTC network gets congested and the timestamps can’t be written, confirmations on the PoS chain will stall. The whole protocol also depends heavily on Babylon’s own relay network, the Relayer. If something goes wrong there, it will impact the transmission of security.

So I think the timestamping protocol isn’t really a product for improving speed—it’s about transferring the PoS chain’s ultimate sovereignty from its own fragile consensus token to Bitcoin’s cryptographic promises. Whether the PoS chain is truly secure doesn’t depend on the number of its validators, but on the timestamp it anchors into Bitcoin. And whether this system can run under extreme market conditions remains to be seen.
#baby $BABY

In the early years, I rented out an idle apartment in the city center to a short-term rental management company. At the time, I thought it was basically free money—I could collect high rent without having to handle anything myself, until my neighbor complained that the tenants turned the place into a party venue and wrecked the entire renovation. That was when I realized the cost of limited asset liquidity and mismanaged control.

Now many people view BABY the same way I did back then: all they can think about is the temptation to get the big pie moving to generate high returns.

Let’s strip away the grand narratives about unlocking Bitcoin value and look at its core logic. This @BabylonLabs_io protocol isn’t performing some kind of high-difficulty DeFi leverage. It simply uses sophisticated cryptographic commitments to freeze your BTC’s right to move for a certain period of time. It turns your coins into collateral for some kind of credit backing, and lends them to other PoS chains that lack initial trust to help stabilize consensus.

You’re not saving money—you’re renting out the immutability of your assets.

As for those striking returns you see on your balance sheet, they are essentially the risk premium paid by the party leasing the assets. These emerging chains need to borrow Bitcoin’s strong security to prevent reorg attacks, so they can only continuously mint their own tokens to pay this expensive rent. The project team demonstrated very sharp insight into PoS chains’ demand for security and Bitcoin holders’ greed for yield, and built this kind of transit market.

However, last weekend I worked through its technical proposal in detail and found an unsettling reality: the asset exit process is extremely inflexible. Once you choose to stake, your BTC is tightly locked in a time lock. When the crypto market faces an extreme liquidity crisis or a policy shift, you can’t quickly liquidate or transfer these core assets. What’s worse, if the network gets congested, un-staking may also require paying extremely high fees.

So in the face of the current market’s frenzy for it, I choose to stay rational. It’s indeed a clever tool for improving capital efficiency, but it is absolutely not a risk-free channel for value growth. The essence of the returns is essentially betting on other chains’ tokens appreciating using liquidity vacuum and network congestion risk. Until I see a more flexible exit mechanism—or experience a real market crash and survive it—I would never take my core assets and risk them on this.
#baby $BABY

🌍 Put COSM in a bigger context:
In 2026, the digital credential track is being reshuffled.
Traffic acquisition costs are rising, and users are becoming more selective.
There are not many projects that can solve both "trust" and "incremental growth" at the same time.
COSM tackles trust with three institutions.
It drives incremental growth through on-the-ground promotion across dozens of cities.
It improves retention by reinvesting the returns.
Answering all three questions at once—whether it’s done well or not—the market will decide.
#COSM
#比特币挖矿难度或下调1.2%

Yesterday, I spent two hours going through BabylonLabs’ whitepaper, especially the section on Bitcoin Timestamping.
I found that everyone’s excitement has gotten a bit off track—they’re all focused on BABY rewards from BTC-pledge mining. But BABY’s real core is that it’s running a business of producing security outputs in reverse.

What I found is that its earlier narrative was: Ethereum exports security outward via L2. But BABY’s idea is: export Bitcoin’s absolute security to a Proof-of-Stake (PoS) chain.
The key logic is clearly laid out in the whitepaper: it solves PoS chain Long-Range Attacks and the problem of overly long unbonding periods.

I think this is a necessity for PoS chains like Cosmos. In the past, Cosmos ecosystem chains typically required 21 days to unbond.
That’s to prevent validators from withdrawing immediately after behaving maliciously.
And BABY uses Bitcoin’s timestamping service to effectively lock the PoS chain’s checkpoints (Checkpoints) inside Bitcoin’s UTXOs.
Because Bitcoin is irreversible, the security period of the PoS chain can be shortened directly from three weeks to just a few hours.

But when I went back and carefully worked through the logic for retail participants, I found an awkward fact: the path for capturing value for the BABY token itself is too long.
New PoS chains need to pay BABY to buy Bitcoin timestamping security. But that revenue depends on how many “okay quality” chains need this service. High-quality chains—like Ethereum itself—such as Solana for now, don’t need an enhancement at that level.

However, for retail users to earn returns, the mainstream approach is participating in native staking for quota races like Cap-1/Cap-2.
Locking BTC in native UTXOs is clean, but it lacks liquidity. @BabylonLabs_io

My current view is: Bitcoin timestamping is a great infrastructure invention. It greatly strengthens cross-chain trust, especially for the Cosmos ecosystem. But for retail users, if you’re only trying to speculate on the BABY token, you need to consider whether its inflation rate and its ability to capture fees from real business match up. If you’re a long-term BTC holder and don’t want to take the risks of wrapped assets—if you just want to treat BTC as a gold-standard asset and earn some B-Yield—then native timestamp staking is the only path, even though the quota is hard to抢. This is still an institutional game of long-term capital allocation, but retail users’ capital efficiency is too low.
#baby $BABY

These days the overall market has been rising steadily, and I haven’t been idle either—I’ve been closely watching Babylon’s moves, and the more I look, the more I find it kind of interesting.

A couple of days ago I saw that Babylon Labs teamed up with Ledger to provide native signature support for a trustless Bitcoin vault. In other words, if you use a Ledger device, you can directly operate vault transactions—you don’t have to keep messing around with all kinds of messy bridging or wrapping. Ledger has sold more than 8 million devices globally. This integration effectively lays the BABY entry point directly in front of a huge base of hardware-wallet users.@BabylonLabs_io

And then there’s Aave: Babylon proposed native Bitcoin collateralized lending on Aave V4. Users lock BTC directly on the Bitcoin network, then borrow assets on the Ethereum side through Aave. No wrapping of BTC, no cross-chain bridge, and no custodial institutions required. Even Aave’s founder said this could potentially unlock more than $4 billion in liquidity.

I also saw that the testnet is already live.

I looked at the data: Babylon now has 56,853 BTC locked in its staking vault, with TVL exceeding $5.6 billion. To be honest, at this size it’s already not small in the BTCFi space.

My personal view is: I think the direction Babylon is taking is right. It doesn’t chase flashy concepts—it's genuinely enabling Bitcoin holders to participate in DeFi without giving up control. But this space is also highly competitive. Whether it can really break out into the mainstream still depends on whether the ecosystem can truly take shape.

Personally, I’ll keep holding onto BABY and observing for now—I’m not in a rush to take action.#baby $BABY

While reading the documentation for @NewtonProtocol , I noticed a line—“Newton provides cryptographic proofs of the correctness of strategy execution via operator networks.” The line is not wrong, but it isn’t right in the way you might want it to be.

The key is—“the correctness of strategy execution,” not “the correctness of the strategy outcome.”

Let’s take an example. The policy rule is “only allow transfers to non-sanctioned addresses.” The operator pulls the sanctions list from the data source, checks that the recipient is not on the list, and the signature is passed. A zero-knowledge proof would prove that this judgment—“the computation is correct.” But if the sanctions list itself is outdated, wrong, or tampered with, then no matter how precisely the operator computes, the result is still wrong.#Newt

Newton solves “computation can be verified” with cryptography, but it cannot—and does not—solve whether the input data is real. This is the classic dilemma of oracles: almost every on-chain system that relies on external data can’t get around it.$NEWT

Now look at the reliability of the data source. The compliant data sources Newton currently connects to mainly include RedStone’s price feeds and Credora’s risk ratings. These companies’ data updates are delayed—from when a new address is sanctioned to when the data is stored in the system, it may take hours or even days. During that window, Newton’s policy engine will treat an address that is actually sanctioned as “not sanctioned.” Users think they’ve received compliance guarantees, but what they actually get is delayed guarantees.

The price-oracle scenario is even worse. In DeFi, many strategies need to reference prices—for example: “reject if the trade price deviates from the market price by more than 5%.” If this “market price” comes from a single data source, then once it is manipulated (which has happened many times historically), Newton’s strategy engine will make wrong judgments accordingly. RedStone says it “has not seen incorrect pricing events so far,” but “has not happened” doesn’t mean “won’t happen.”

The most clever part of Newton’s verifiability narrative is that it directs users’ attention to “on-chain verification,” causing them to overlook the “off-chain data” piece. Users see a zero-knowledge proof and feel reassured, when in fact the real risk lies in the areas the zero-knowledge proof doesn’t cover.

A cryptography-wrapped black box is more dangerous than a plain black box—because it makes you think you can see clearly.

These past days I’ve been seeing posts about Grvt everywhere on the square. Honestly, I think I have the most say when it comes to Grvt. The first time I got in touch with Grvt, I did it with the mindset of “scooping up free money.” It went live on the testnet at the start of the year. The testnet experience was smoother than I expected. Opening and closing positions felt like there was almost no delay—basically no different from using a centralized exchange.

Later, when Season 2 started, I put some money into it. What truly made me feel that this actually has something to it was the GLP vault. I deposited 10,000 U. I earned while using the points—every month I was credited over $80, and the annualized return is roughly 11%. The key is that the money isn’t locked. If you want to trade, you can take it out anytime and use it.

Before Grvt launched, they ran a test where you had to fill out a bunch of questions, and in the end you get an animal tag. Mine came out as an alligator. It looks inactive on the surface, but I kept observing. It likes to keep money in yield strategies—and it’s pretty accurate, honestly. I’m never the type who stares at the candlestick chart every day and constantly enters and exits. I’m more used to letting funds roll slowly and then stepping in when the opportunity comes.

About the airdrop registration—there’s a detail I want to remind you of. In a few days, on the 17th, the deadline to fill in the claim/receiving address will be over. This is important—make sure you do it ASAP. Remember, remember!
GRVT’s airdrop has a multiplier plan: you can choose to delay claiming the tokens. If you wait 4 months, you get double; if you wait 8 months, you get four times. But I still chose to claim immediately—who knows how much is left after a few months!

One last thing.
Grvt TGE is July 21st, total supply is 1 billion, and the community airdrop is 28%. I don’t have many points—@grvt_io probably won’t get many tokens. Let’s see how it performs in real life after launch first. If the price is right, I’ll sell everything. The money you end up with is the money that truly belongs to you! #grvt

The 9th anniversary tasks are finally done! I hope I get 1 BNB for the ultimate grand prize! Wishing Binance a happy 9th anniversary! I’ll still be with you for the next anniversary celebration!
#BinanceTurns9

To be honest, last week I helped a friend withdraw money from a vault. The money was clean, but it got stuck in the middle and we ended up waiting most of the afternoon. Customer support said, “This is Newton doing pre-settlement authorization.” I was completely baffled on the spot—I'm moving my own money, so why does it have to go through Newton's review first?

The more I thought about it, the more it felt like Newton took the traditional finance logic of “approve first, release later” and welded it directly onto the blockchain. Rego writes the policies, EigenLayer operators vote, and data sources like Chainalysis and RedStone prop up the whole thing—it sounds very hardcore, but I just want to ask one question: when DeFi first took off, wasn't it because of those four words, “permissionless”? Now every transaction of mine has to wait for a group of people to vote on whether it passes or not. How is that any different from lining up at a bank counter? @NewtonProtocol

What I find even harder to understand is that Newton says it is credibly neutral, but who actually writes the policies? As an ordinary user, I don't even have the right to change how my own money is evaluated. TEE and ZK proofs sound impressive, but if the operators collude and act maliciously, what am I supposed to use to verify that the attestation is real? Isn't that still a black box, just wrapped in a different “transparent” label?

Cross-chain scenarios are even more troublesome, because the policies have to be executed synchronously across multiple chains. If the data source is delayed or the oracle reports an error, my funds just have to sit there and wait. The AI agent scenario sounds like the future, but to me it looks more like putting a gatekeeper on every step an agent takes. Institutions at least get a “compliance-reviewed” liability shield. What do I get out of it?

Later I thought about it: why should I pay for a policy I had no part in creating? Newton packages this whole process as an “authorization layer,” but as a retail user, I don't even have a say in it. Institutions use it happily, and if something goes wrong, Newton takes the hit. But what about me? The money is clearly mine, and I signed the transaction myself, but whether it can move is decided by a bunch of nodes and data providers I don't even know.

DeFi taught us, “not your keys, not your coins.” Now Newton is telling me that having the key isn't enough—I also have to pass its approval. I can't make sense of that math. #newt $NEWT

Hey Newton, I’ve been wondering about something lately—does it really count as decentralized?

The whitepaper is quite well written, and there’s a line in Binance Research’s report: “Progressively decentralizing the Protocol by onboarding third-party validators to secure the Newton Keystore rollup.” “Progressively”—meaning it’s not yet. #Newt

MEXC’s guide is more direct: “Progressive decentralization roadmap transitions from foundation control to full community governance through four phases.” Four phases, transitioning step by step from foundation control to community governance. The question is: which phase are we in right now? I searched through all the public materials and couldn’t find any explanation of how ordinary users can independently run validation nodes. Gate’s encyclopedia, however, is very clear: “Validators are responsible for validating transactions and maintaining network security, while delegators indirectly participate in network security by supporting validators.” Ordinary users can only “delegate”—that is, stake to nodes controlled by the foundation; they can’t become validators themselves. $NEWT

What worries me even more is the power held by the foundation. Keystore Rollup uses dPoS consensus, and validators need to stake NEWT to secure the network. But in the early stage, network nodes are led by the foundation. The Magic Newton Foundation received $1 million in funding from Magic Labs and has never raised any funds from investors. The foundation controls most of the non-circulating tokens and the network’s validation nodes, and can unilaterally modify consensus rules, freeze the staking pool, and adjust the slashing logic—yet none of these powers are constrained by any terms in the documentation.

A so-called “decentralized” protocol that doesn’t let regular people run validation nodes, with the consensus rules decided by the foundation. What’s referred to as “progressive decentralization” looks, at least for now, more like a long-term promise meant to soothe the community rather than a reality that has already been implemented. “Decentralized infrastructure” is still determined by the foundation for now. @NewtonProtocol

A “decentralized” protocol that doesn’t even allow ordinary people to run validation nodes—are you sure it’s actually decentralized right now?