Daft Punk–不是反指版

Hilarious—those old brothers who are still stubbornly holding long positions at $SPCX . I genuinely can’t believe it. You rushed in when the IPO was $135, it went up to $225 but you wouldn’t sell, and now it’s down to $110—you’re still there talking about “long-termism” and “Mars faith.” Can faith fill your stomach? Can a tweet from Musk make your account recover?

Look at this chart. It’s only been a little over a month since listing, and it’s been cut in half straight from $225. Short positions have piled up to 32% of the float. And there’s $25.0 billion worth of “ammo” blasting right in your face, yet you’re still there “buying the dip” and “adding to your position.” When the lockup expiration wave hits on August 6, 900 million shares will directly dump onto the market—that’s $116.0 billion of sell pressure. How do you expect to catch all that? The float is less than 5%—if any major shareholder wants to cash out, the stock price basically falls freely.

Even if Musk comes, it won’t help. I’ll tell you: even if Musk really shows up, it still won’t help. This stock is valued at over 100x sales and has been losing money consistently. ROE is -33%. The valuation is propped up entirely by the “space + AI” story. Once the story ends, where’s the money?

Starlink does make money, but can it support this big family—rockets, AI, and Twitter? What came out of that $60 billion Cursor acquisition deal? What’s the integration actually produced?

I’ll be blunt: SPCX will hit double digits. Under $100 is basically a lock. My short position is already maxed out, and I’ve got plenty of leverage. This lockup expiration wave is when I get rich. You longs keep chanting your mantras—I’ll keep counting my money. Later, when SPCX drops to $80 or $90, don’t blame me—I warned you. This isn’t Tesla—there’s no retail crowd saving the day. Only institutions dumping.

Musk? If he comes, he’ll end up crying too.

LOL, even the neighbor’s withdrawal feature costs money to purchase. It’s trash.

I just cut the Ether, and hopped onto a scumbag dog’s ship—so we’ve agreed to alternate increases, right?😅$DOGE

Our privacy compliance testnet ran for three weeks—Dusk got stuck in the toolchain rather than the consensus

Deploy a contract with confidential balances on the testnet, and the PlonK circuit compilation time for @Dusk came out nearly double what we expected. It’s not fatal, but the “segmented toolchain” feeling is very clear: from a local node to the browser-side signing, we often have to manually switch RPCs, and the documentation examples don’t match the latest version.

Secret Network’s development experience is smoother, but I’ve never been fully comfortable with its TEE trust assumptions.

Dusk wants to go down the path of compliant finance—binding private transactions and identity verification at the same layer. The direction is right. But in practice, zero-knowledge proof generation is still more demanding than typical general-purpose hardware, and the verification nodes also have quite high memory usage. Oasis has modularized the privacy layer, making development more flexible, but its on-chain identity and compliance components aren’t as tightly integrated with the chain as Dusk’s. In the asset issuance process I tested, Dusk’s permission design is more granular: it can distinguish between issuers, auditing nodes, and regular holders. That makes it more practical than chains that only support anonymous transfers.

The issue is also here. Dusk’s developer barrier is raised by compliance parameters—many configurations require understanding regulatory terminology before you can get started, so ecosystem cold-start may be slower than expected. $DUSK has a clear fee and governance-token logic, but the types of applications that can be deployed on-chain are still somewhat limited. Aleph Zero’s privacy contracts are more general-purpose, and its Gas is more stable, but in regulated-asset scenarios it lacks a native compliance framework.

If Dusk could package the SDK a bit thinner and turn compliance parameters into preset templates, the developer experience would improve a lot. Otherwise it feels more like a chain customized for institutions than a place where ordinary developers can quickly try things and iterate. At least from what we see now, consensus works—the bottlenecks are the tools and the documentation.

#dusk

TermMax’s liquidation line looks impressive—thinner liquidity still doesn’t help

Compare the borrowing interface of @TermMax side by side with Aave V3, and the liquidation parameters differ pretty straightforwardly. TermMax’s collateral ratio cap is looser than Aave’s; when the health factor drops below 1.05, partial liquidation is triggered. This threshold is quite aggressive among mainstream lending markets. The liquidation discount and buffer time are interesting, though: TERM stakers can participate in liquidation auctions, so it’s not entirely robot front-running. But because the pool depth is shallow, if someone posts a slightly larger order, slippage can be too big to contain.

Compound’s liquidation line is more conservative. Liquidators take a fixed discount, the path is simple but not flexible. TermMax splits liquidation into a Dutch auction, where the marginal price decreases gradually; in theory, that’s more friendly to borrowers. The problem is that when the market inserts a spike quickly, TermMax’s auction time window is a bit too short—borrowers don’t have time to top up collateral before they get auctioned off. Shallow liquidity amplifies this flaw. For users staking TERM, if they don’t actively monitor liquidations themselves, their returns may not be as good as using liquidation bots on Aave.

This isn’t unique to TermMax; it’s more like a common issue with fixed-term lending regarding liquidation. It shifts risk from interest-rate fluctuations to a time dimension, and once triggered there’s almost no room to maneuver. Transparent rules are a good thing, but when the chain is congested, oracle update delays can cause liquidation prices to deviate from actual executed prices. Compound has this problem too, but with a deeper pool, the discrepancy is diluted.

Overall, TermMax’s liquidation mechanism suits professional players who are willing to watch the market closely—not retail users who place an order and then go to sleep. If TERM governance can reduce the liquidation discount or extend the auction buffer time, it would be more stable. For now, I’m only testing with a small position—I won’t move my main collateral over.
#termmax

Can an angry ordinary person instantly transform into a genius trader?
Of course not.$ETH

To be honest, I don’t recommend becoming an Air Force pilot right now—I got bewitched and trapped. After reading the SEC’s new crypto-asset regulations, I feel like the altcoin season may really be coming.

In plain terms, the SEC’s new rule is basically one thing: they won’t go after people; instead, they’ll issue you a “birth certificate.” Regulation Crypto Assets, released on August 18, allows project teams to raise funds without registration. For small projects, the maximum is $5 million over four years; for bigger ones, it’s capped at $75 million per year. It also provides a safe harbor—once a project is truly decentralized, with no one in charge, it’s no longer considered a security. Previously, building a project felt like doing theft—you were always afraid of being sued. Now it’s as if the authorities have drawn an official lane and opened the road for you. In the short term, it’s a loosening for the industry and a positive development. In the long run, it means crypto has officially been brought into the U.S. financial system, and the days of the rough-and-ready “outlaw” era may be over. $ETH

It's too much like the seventh night of the seventh festival that feels like I took Viagra—holy crap $ETH

Posting seems to get about the same income; looks like I also need to find a job as a security guard 😂$DOGE

@TermMax is TGE in five days away. I’ve gone through the official documentation and a few rounds of third-party data a number of times. What concerns me the most isn’t the points—it’s their carefully packaged “physical-delivery settlement” mechanism.

The official says that when markets are highly volatile, they won’t do forced liquidation. The collateral is transferred directly to the lender, as they put it, “to preserve the value of assets.” It sounds considerate, but if you think about it closely, this isn’t eliminating risk—it’s shifting risk. When borrowers get liquidated, the lenders end up having a pile of collateral shoved into their hands, including the tokenized stocks of the kind RWA they’re pushing. I lend out USDC to earn fixed interest—so after liquidation, I’m supposed to go find buyers to realize it at a discount? At the moment of liquidation, doesn’t the “guaranteed yield” narrative fall apart?

Even more striking is that the whitepaper lists liquidation fees right out in the open as treasury revenue, positioning them as value flowing back to TMX stakers. In a lending protocol, using “someone getting liquidated” to generate token lifeblood—does this incentive direction really look healthy? The more aggressive the borrowing, the more frequent the liquidations—stakers receive more. Is that encouraging credit, or encouraging leveraged bets?

The data also doesn’t add up. The official claims TVL is over 90 million, but third-party monitoring in May shows it was around 31 million. The whitepaper says 64 million. Threefold growth in three months—right coinciding with the points-to-airdrop phase. How much of that is mercenary capital deployed specifically for TGE? And once the tokens are generated on August 25 and rewards stop, how much is likely to remain?

Next, consider the 18% APY promised by the Neutral Trade treasury: the base yield is only 4%. The remaining 6% comes from TMX airdrops, and 8% is from the project team “making up the difference” using TMX that hasn’t been listed yet. More than half the returns rely on future tokens to backstop the deal. Isn’t that essentially buying today’s growth with tomorrow’s sell pressure?

I don’t deny it’s brilliant how they’ve turned Uniswap V3 into an interest-rate AMM. But the liquidation risk shifts from borrowers to lenders, growth relies on token subsidies, and value flows back via liquidation fees. After the tide goes out, how much of that 90 million is real belief? What do you think?
#termmax

Dusk’s privacy compliance narrative doesn’t survive a single failed sync.

I re-ran the test environment for @Dusk , didn’t look at the official talking points—only cared whether it can support the claim about an on-chain compliance RWA layer. After finishing the node run, the impressions were very direct: the narrative is more mature than the engineering. Block synchronization isn’t slow, but the zero-knowledge proof generation step often makes the workflow unpredictable; the state browser updates are also lagging. Troubleshooting mostly relies on digging through past community history.

Dusk’s privacy design has ideas, but at the operational layer the roughness is obvious.

Compared with Polymesh, it’s even clearer. Polymesh places identity and compliance checks at the chain layer, so developers don’t have to assemble everything themselves; the tradeoff is sacrificing privacy elasticity. Dusk takes the opposite approach: treat privacy as the default layer, and complete compliance through configuration. The direction aligns better with institutions’ needs for data isolation, but the documentation doesn’t clearly explain the configuration logic. I tried to walk through an asset issuance flow and got stuck multiple times between permissions and proofs. In the end, I suspected I misunderstood rather than the product logic being at fault.

Bringing Ondo and Centrifuge into the comparison, Dusk’s positioning is more foundational. It doesn’t have a ready-made liquidity entry like Ondo, nor does it have asset-side interfaces like Centrifuge. This isn’t necessarily a flaw, but it means on-chain asset settlement will be much slower. Without meaningful on-chain asset settlement, the value of a privacy compliance layer is hard to perceive. Ultimately, Dusk’s ability to capture use cases doesn’t depend on how clever the technical route is; it depends on whether real assets are willing to stay on-chain. As of now, Dusk still feels like it’s in the stage of proving that this proof framework skeleton can work.

#dusk $DUSK

Playing memes: you must never buy a curved screen 😅$牛来

Turn Fixed Interest Rates into an Auction Arena. TermMax’s Liquidity Ledger Is Tighter Than Expected

After getting started with @TermMax , the most immediate impression is that it fully hands interest-rate pricing power over to periodic auctions, removing the need for the market-maker layer. The protocol feels light; the burden shifts to users. For less popular maturities, auction depth is thin—make a slightly larger bid and it pushes the settlement line off in an ugly way. Here, $TERM feels more like subsidized fuel to incentivize liquidity; the path to value capture still hasn’t really run.

The divergence between TermMax and Pendle is very clear. Pendle splits future yields into PT and YT; liquidity then rolls into the AMM, and exits are smooth. TermMax doesn’t tokenize yield. Once a fixed rate is locked, if you want to exit early you can only find a counterparty in the secondary market. This design reduces the complexity of the arbitrage layer, but sacrifices flexibility. In practice, Notional’s fixed-term lending is more convenient, and the AMM at least provides some slippage buffer. TermMax’s auctions often fail when the maturity isn’t actively traded, and capital efficiency takes a hit.

On the collateral side, TermMax is broader than Pendle, which is worth calling out. It allows more long-tail assets in; liquidation thresholds are conservative, so liquidation/collapse risk is lower—but capital utilization is also squeezed. Aave’s e-mode can raise efficiency for similar collateral types quite a bit; TermMax doesn’t have anything comparable yet. Right now, $TERM doesn’t appear to be strongly tied to protocol revenue, and its governance voting weight is low. If an interest-rate protocol’s token is only used to distribute rewards, it’s hard for the secondary market to assign durable valuation.

There’s also an issue with interest-rate oracles and auction manipulation. Large bids can temporarily distort the winning interest rate. In the cold-start period, there’s no market-maker hedging, so the bid-ask spread can be pulled above actual funding costs. This isn’t fatal, but it will make institutions hesitate. For TermMax to really break out, it must make $TERM’s cash flows or fees concrete—otherwise, compared with other auction-style interest-rate protocols, its difference will remain only at the interface level.

#TermMax

Using zk stack finance for privacy—Dusk still needs one more breath before it’s truly usable

I care a lot about practical, compliant deployment of privacy chains. Recently I reran Dusk and it feels like its roadmap is closer to institutional scenarios than most privacy chains. But the engineering issues are also exposed pretty directly. @Dusk pushes the compliance logic into the proof circuit rather than relying on an identity layer like Concordium does. The abstraction is cleaner, but the added complexity gets entirely shifted to the validator nodes and developers.

Comparing Secret Network and Oasis makes this clearer. Oasis’s privacy computation focuses more on data availability, while Secret offers greater flexibility with general smart contracts. Dusk narrows its focus to tokenized securities. This trade-off makes the compliance structure heavier, but regular users will first feel that the toolchain is thin. Dusk’s node synchronization and RPC sometimes stall; in the browser, transaction fields can take a long time to appear. That’s not friendly for people who just want to verify a single transfer. The zk proof strength isn’t bad, the PlonK direction is reasonable, but the infrastructure completion is a step behind.

From a staking perspective, $DUSK ’s return model is rather conservative, and the rules for unlocks and slashing are written vaguely. I don’t classify this as a mechanism flaw; more that the product hasn’t truly treated validators as users. In a compliant financial chain, if key parameters are hidden, outside capital will hesitate. Long-term stakers will find it hard to form stable expectations. Dusk’s privacy-securities narrative is fine; what’s missing is clearly explaining the costs of operating nodes.

Overall, Dusk has found a less crowded intersection between privacy and compliance, and it’s more solid than simply pushing a privacy narrative. But if, after mainnet, the toolchain, browser, and validator experience stay as they are now, even the best zk abstractions will be held back by usage costs. For now, I’ll keep watching version iterations rather than jumping to conclusions.
#dusk

Sun Ge says, all crows are the same black; if it’s not a crow, then smear him 😂$BTC

Tear off the cloak of fixed-income returns: TermMax’s real leverage experience and liquidity trade-offs
Capital efficiency is always the core proposition of DeFi. Recently I went to test TermMax’s fixed-rate lending and leverage mechanics. Most protocols talk about expected returns, but there are only a few that really lock lending costs into a fixed range. TermMax aims to smooth over the experience gap between traditional fixed income and on-chain finance. Looking at the expected APR on the interface, the first thought that flashed in my mind was that it’s essentially competing with Pendle for the same pool of liquidity seeking stability.
When I actually used the range order tool with @TermMax , the sense of deja vu was too strong—it’s basically hard-wiring Uniswap V3’s liquidity ranges onto an interest-rate curve. Depositing USDC or ETH to earn a fixed rate is indeed smooth, but the depth issue shows up immediately. As a platform built around predictable yield, if TermMax doesn’t bootstrap the initial pools with serious depth, slippage will wipe out the already thin spread in no time. With FT and GT tokens representing yield rights and lending positions in hand, exiting becomes extremely dependent on the AMM’s real-time performance.
What needs the most scrutiny is TermMax’s one-click leverage loop feature. Packaging the process—collateralizing, borrowing, and reinvesting—into a single transaction sounds convenient, but at the base it’s still risk stacking. Compared with Aave, which requires you to manually calculate the health factor, TermMax’s automated execution is certainly easier. The catch is that once you crank up the leverage multiple and run into extreme market conditions, this kind of black-box liquidation risk is effectively pushed entirely onto retail users.
The space isn’t short on protocols inventing new buzzwords; it’s short on real yield models that can survive across market cycles. TermMax wants to use a customized AMM to capture both sides of the fixed-income and leverage markets—but at this stage, the experience still feels like a clever yet fragile lab product. Rather than selling the narrative, it should first solve the liquidity loss problem when exiting. #termmax

Compliance-chain cold start, Dusk still lacks convenient tools

Reading through Dusk’s implementation docs, the team wants to turn regulatory compliance into a consensus-layer primitive rather than just adding a KYC switch in the wallet. The direction is right, but the cold-start phase has real problems: the asset creation flow is heavy, and the debugging tools EVM developers are used to have not caught up. Dusk wants to lower the barrier, but in practice you first have to understand its state model, which by itself filters out a chunk of people.

The contrast with Polymesh is clearer. Polymesh’s securities tokenization path is straightforward, with clearly divided responsibilities between asset templates and compliance nodes, but its openness is questionable, making it feel more like a consortium chain. Dusk’s privacy layer is intentionally designed to be regulatory-friendly, which follows a different logic from Secret’s default anonymity. Dusk is suitable for institutions that want to move RWA on-chain without exposing holdings, but for ordinary DeFi users, this privacy model is relatively heavy, and the interaction path is longer than on general-purpose chains.

The validator side is even more worth paying attention to. Dusk consensus ties settlement finality and compliance checks together, which is theoretically more robust, but validators have to maintain a more complex state, and the incentive returns are not transparent enough. Compared with Ondo, which packages compliant assets into simple yield products, Dusk chose a more foundational path. The trade-off is a quiet ecosystem, with sparse wallets and indexers. A big vision does not mean a fast cold start.

Overall, @Dusk is stuck in the middle ground: privacy is good enough but not as complete as Secret, compliance is direct enough but not as quick and simple as Polymesh, and the tooling is not as convenient as on general-purpose chains. For this chain to take off, narrative alone is not enough; it first has to solve developers’ frustration.

#dusk $DUSK

$DUSK These days the fluctuations aren’t that big, and it’s actually making me a bit unsure. When the market isn’t noisy, it’s usually either because there’s no narrative, or everyone’s waiting for something. Dusk has been talking about going down the path of compliance and privacy—different from those purely anonymous projects. What it wants is privacy that institutions can accept, with auditability and regulatory oversight. Honestly, this direction is quite timing-sensitive.

#dusk A lot of people below are still asking about the mainnet progress and staking. My own feeling is that the ecosystem isn’t at the stage where it can run on its own yet. With few on-chain applications, the money can only circulate within the token itself. Even if staking yields are high, if it’s basically just locking up supply and consuming liquidity, it can hold up in the short term—but in the long run you still need real assets or real business getting put on-chain. Without applications, gas demand won’t really ramp up, and buy-side demand is mostly just expectation.

@Dusk ’s bet on RWA and financial infrastructure makes sense logically. For traditional institutions to go on-chain, the biggest fear is data being exposed—compliance-grade privacy is almost a must. The hard part is how to get regulators to nod, and how to make developers willing to come in and deploy. As long as those two issues aren’t solved, the token is still mainly a sentiment asset. Look at how the market values it—high one moment, low the next—which shows people haven’t formed a consensus.

Sometimes I also wonder if I’m overthinking it. In a position like $DUSK , it’s more like waiting for a breakout in volume or a piece of news. Once it actually arrives and you chase in then, it’s a different story. For now, I can only observe with a small position and not do anything rash. Instead of watching other people shout orders, it’s better to check whether there are new contract deployments on-chain—those can’t really be faked.

Another point: the token unlock schedule. If liquidity suddenly increases while staking doesn’t keep up, the price will likely feel uncomfortable. You’ll need to look it up yourself—don’t rely on secondhand info.

That’s about it. No conclusion—just watching and thinking as I go.

Every time I open the official documentation for @Dusk , I feel a kind of security obsession that’s almost paranoid. Code audits, community votes—these seemingly procedural actions are, in reality, the entire team publicly dissecting itself. Traditional projects are used to a “one-time release,” while Dusk feels more like an iteration experiment that never stops—this is why I decided to keep a portion of $DUSK in my wallet, not for anything else, just so I can cast my vote in governance proposals and personally experience the weight of decisions.
What truly surprised me is the stability of Dusk’s privacy protocol in cross-chain scenarios. Once, during a cross-chain transfer, I only took a few steps, and the on-chain information was naturally obfuscated—so external observers couldn’t track it at all. In that moment, I realized that privacy shouldn’t be an academic concept locked away for later; it should be as natural as breathing, seamlessly integrated into every transaction. Real privacy should be effortless and smooth—something users shouldn’t have to intentionally do.
The community’s engagement is equally impressive. Whenever new features go live, developers hold an AMA in the community channel, answering questions one by one. I like joining these discussions because they often help me catch sight of where the project is heading next. This sense of transparency has given me even stronger confidence in the long-term value of $DUSK .
Looking back over these past few months, I’m growing more and more convinced that what the Dusk Foundation is building is an ecosystem of “privacy-as-a-service.” What it provides isn’t just technology—it’s also cultivating a group of users who truly know how to protect their own data. I’m excited to see more decentralized applications integrate Dusk’s privacy layer in the future, so that every on-chain interaction feels like a private conversation, not an open broadcast.
If you’re also interested in privacy technology, I recommend following @Dusk’s official channels, participating in community activities, and experiencing the features of $DUSK for yourself. In this decentralized world, let’s protect our data sovereignty together.#dusk

I’ve been thinking that the truly interesting part of $DUSK probably isn’t the word “privacy.”

There are many privacy chains, and there’s no shortage of compliance narratives, but most projects seem to stand at one of two ends: either hide everything, or lay everything bare. @Dusk wants to be more like that narrow middle path. Keep what needs to be confidential confidential, keep what should be transparent transparent—during authorized review, disclose selectively, and ensure settlement is definite and fast. This direction isn’t flashy, but it feels like what real finance actually needs.

With the DuskEVM mainnet coming soon, I’ll be paying more attention to Hedger. It’s not just adding a privacy layer to EVM; it integrates homomorphic encryption and zero-knowledge proofs into confidential transaction workflows. Developers can keep using familiar Solidity, while institutions don’t have to expose their positions, counterparties, and full trading logic. Whether it can run smoothly is crucial.

Dusk Trade is also worth watching. Money-market funds, ETFs, bonds, RWA—if it can truly complete issuance, trading, and settlement in the form of a compliant platform, then Dusk won’t just be infrastructure; it will be moving closer to the financial application itself. Add the Chainlink collaboration, participation from regulated entities, and the native issuance path, and the room for imagination really is opening up.

But I won’t rush to a conclusion. It’s not hard to make a technical narrative sound beautiful; what’s hard is asset scale, real users, and ongoing settlement volume. Next, there’s only one thing to look at: whether institutions have really moved their business processes onto it.

If they have, the story changes. #dusk