兰精灵

#nil $NIL @Nillion Yesterday, I was chatting with a few friends, and somehow the conversation circled back to Nillion. That evening, I decided to go over its technical roadmap from start to finish again. The more I read, the more I felt that the project was heading in a very different direction than before.

In the early days, when people talked about Nillion, it was mostly about privacy-preserving computation and AI storage. Now, the focus has clearly shifted to Encrypted Markets, with Covenants at its core. Put simply, you can encrypt stop-loss orders, auction bids, or other instructions and put them on-chain ahead of time. No one can read their contents until the conditions are met. Once the price or time threshold is reached, the nodes automatically decrypt and execute them. This could be really useful for DeFi. On-chain trading intentions are currently exposed too early, making them easy prey for MEV bots. Covenants could help fix that vulnerability.

And this isn’t just theory. The Dusk phase is already live on Ethereum mainnet, bringing Covenants to L1 for real. There’s also a clear seven-step roadmap ahead: Darkfall expands to multiple EVM chains, including Arbitrum and Base; Skyglow enables triggers on one chain and settlement on another; Nightside supports any verifiable data source; Neon introduces a dedicated language and VM; Aurora adds post-quantum security; and Moonshine focuses on lowering costs and scaling up. Every step is aimed at greater scale, lower costs, and stronger security.

In terms of applications, I’m personally most excited about sealed stop-loss orders and sealed-bid auctions, where strategies remain completely hidden until they’re triggered. Looking further ahead, if AI agents begin trading autonomously at scale, this encrypt-first, execute-later model could become a foundational piece of infrastructure. After all, the last thing machine traders want is for their intentions to be revealed in advance.

Of course, an appealing roadmap doesn’t mean the technology is already proven in practice. Ultimately, it’ll come down to developer adoption, the number of real-world applications, and the reliability of the node network. The next generation of DeFi won’t compete on TVL and trading volume alone; it’ll also be about protecting users’ strategies while remaining verifiable. If Covenants can deliver on its promise, Nillion is worth keeping an eye on.

#美国PPI同比升至6.3% U.S. PPI rose to 6.3% year over year in September, confirming persistent inflation; crypto markets should watch for macroeconomic pressure

The latest data from the U.S. Department of Labor show that the Producer Price Index (PPI) rose 6.3% year over year in September and 1.3% month over month. Core PPI also exceeded market expectations. A rebound in upstream inflationary pressure has raised expectations that the Federal Reserve will keep interest rates high or raise them further, supporting Treasury yields and the U.S. dollar index while weighing on risk assets across the board.

For crypto markets, risk assets such as BTC and ETH are highly sensitive to changes in interest rate expectations. If macroeconomic pressure persists, short-term volatility could intensify, with highly leveraged contracts and large-cap altcoins especially vulnerable to bouts of cascading liquidations.

The market’s central focus has shifted from “inflation cooling” to whether “inflation is picking up again” and whether “the Fed will take a more hawkish stance.” Until the data clearly show inflation cooling, macroeconomic factors may continue to weigh on crypto markets.

At this stage, watch out for sharp volatility around data releases, reduce exposure to high leverage, avoid taking large positions around key data announcements, and manage positions carefully.

#Circle上半年营收约14亿美元 Circle reported revenue of approximately $1.4 billion in the first half of the year: Is the stablecoin business really profitable?

Circle recently disclosed revenue of approximately $1.4 billion for the first half of 2026—a substantial figure in itself.
But when you look at USDC’s on-chain data alongside it, you’ll find that the stablecoin industry’s path to profitability is far more complicated than its headline transaction volumes suggest.

In the first half of the year, USDC’s on-chain settlement volume reached approximately $36 trillion, while total minting and redemptions exceeded $315 billion.
This shows that USDC’s usage frequency, circulation, and on-chain activity are all growing, further strengthening stablecoins’ role as blockchain infrastructure.

But the cost structure is what really deserves attention.
In the first half of the year, Circle spent approximately $819 million on distribution partner revenue shares and transaction-related costs, accounting for about 59% of total revenue.

In other words, although revenue was close to $1.4 billion, nearly 60% went toward channel partnerships, maintaining liquidity, and transaction costs.
This also explains why stablecoin projects often have “high transaction volumes” without necessarily seeing a corresponding improvement in profits.

Competition in the stablecoin sector is no longer just about issuance volume; it’s also about distribution channels, liquidity, and cost control.
For Circle, continued growth in USDC’s on-chain footprint is a positive sign, but whether it can turn high transaction volumes into healthier profits remains to be seen.

What do you think?
With $1.4 billion in revenue and channel costs approaching 60%, does this show that the stablecoin business is “scale first” or a “cost trap”?

#Circle #USDC

Bought bStocks and want to trade futures? Do you need to sell them first?

No need to sell! No need to sell! No need to sell! 🙂‍↔️

You can use them while holding them—and keep holding them while you use them.
One pool of funds, two ways to play.

No need to overthink it—trade on Binance and buy bStocks!
Find all the bStocks you want.

Create an ad with us for a chance to win an iPhone and BNB! 🚀

#币安创意广告大赛 #bStocks #bnb

September U.S. CPI is here! How will crude oil and U.S. Treasuries move after the data comes out?
Key data: Year-over-year inflation rose to 3.7% (from 3.4%), while gasoline prices surged 9.1% in a single month, accounting for more than half of the increase. Core CPI also rose 2.6%.
My take:
1. U.S. Treasuries: They’ve already been directly rattled. Yields had been rising rapidly, and the odds of an October rate hike jumped from around 20% to nearly 50%. Short-term yields reacted most sharply, suggesting the market is repricing a “higher for longer” rate path.
2. Crude oil: CPI is more an “outcome” than a “cause.” The main reason prices are elevated is still supply disruption caused by the war involving Iran. As long as geopolitical risks don’t ease, prices are likely to remain volatile at high levels, continuing to put pressure on inflation and the bond market.
In a nutshell: high inflation pushes inflation higher → higher inflation lifts rate expectations → U.S. Treasuries come under pressure. This chain will be hard to break in the short term. Do you think the Fed will hold steady at the end of October, or hike rates outright? Let’s discuss in the comments.
$BTC
$ETH

#9月cpi来袭原油美债走势如何

The full moon reaches mid-autumn, quietly waiting for blossoms to bloom.
May the market rise like the full moon, gradually entering a better season. Wishing everyone a Happy Mid-Autumn Festival ✨
$BTC $BNB $SOL

Four months of incubation, one day of blooming.

$TLS has officially been announced as the official FLAP test token—both the best reward for everyone’s perseverance and the brand-new beginning for building on the BNBChain ecosystem and pushing forward in the #MemeFi track.

As the newly launched official test token for the ecosystem, TLS is aligned with the established market-cap framework of TST and TUT. Leveraging FLAP’s currently hottest Meme-launch ecosystem advantage, it enjoys unique growth dividends. Unlike many speculative tokens in the market, TLS stands firm through solid community building. With official endorsement, it reinforces the value foundation.

No short-term hype games—only long-term certainty in value. In the future, $TLS will surely continue the market-cap legend of BNBChain’s official test tokens, delivering a perfect answer for every builder who keeps showing up and building.

A pool of clear blue water, with mountain clouds mirrored together.
All before me is gentle—stealing a moment of leisure.
$BTC $BNB $SOL

The seasons turn, and flowers bloom as usual🌿
You don’t have to rush to faraway places—there are also sights to enjoy nearby.
$BTC $BNB $SOL

The market rises and falls, but life has its own rhythm ☕
Catch a strand of warm sunlight, and keep a calm, ordinary heart,
Slow down—it's also a kind of confidence.
$BTC $BNB $SOL

No sun today.
The weather is pleasantly cool, with just the right breeze.

Even the flowers bloom more gently than usual,
so don’t shut yourself up too tightly.

Go a little slower,
give yourself a bit of wind, and leave a little breathing room for your mood.
$BTC $BNB $SOL

A river of setting sun, a landscape of gold 🌅
Rivers rise and fall, and so do markets.
Less impatience, more patience.
Keep a calm mindset, wait for flowers to bloom, and may all your wishes come true.
$BTC $BNB $SOL

One pink, one purple, as summer flowers bloom 🌿
Amid the smoky bustle of everyday life, capturing a moment of romance.

$BTC $BNB $SOL

Hello September, may the wind of this month bring a little new good luck.
$BNB $BTC $SOL
The busyness of August gradually fades away,
and starting in September, the days slowly grow quieter.

No need to rush to chase after something,
and no need to force yourself to have answers every day.
Have a drink you like,
watch the evening wind once,
and let your mood take some time to settle.

This month,
may we all be able to hold our pace,
in the small, everyday moments,
slowly accumulate the light that belongs to us.

Dew covers the morning-glory vines,
when flowers bloom, sometimes rising and falling unpredictably 🌿
All things in the world have their cycles;
wait quietly for the moment—what has settled will bloom.
$BNB $SOL $BTC

This is how the ride-hailing app is often like: they give you an estimated price to mentally prepare you, and then the final bill is calculated by the actual mileage. The same goes for the Gas fee of @Dusk — the cost is simply `gas_used × gas_price`. Gas price is denominated in LUX, and 1 DUSK equals 1 billion LUX. Unused gas doesn’t get charged, but if Gas runs out mid-transaction, the entire operation gets rolled back, and you’re still billed for the calculations that ran earlier. At first, I also thought this setup was a trap. Later I figured it out: if a failure were completely free, hackers could endlessly trigger complex error calls to make nodes waste work—now *that* would be the real trap.

So every time I confirm a transaction, I check three things separately: whether the Gas limit is enough to run the entire process, whether the Gas price is reasonable, and whether the call target and parameters were filled in correctly. If it fails, don’t rush to resubmit—first use the official browser to verify the type, the fee, the amount used, and the location of the error. Naively doubling the limit just feeds more fuel to the wrong contract; it doesn’t really solve the problem.

The flow of fees is also pretty interesting. Each block’s reward consists of a newly issued $DUSK plus transaction fees, which are distributed to the block producer, the development fund, and the council; the portion that isn’t allocated may be burned. When the network is busy, the fee goes into validator incentives—but that doesn’t mean you can just hold coins and earn passive dividends.

What really made me stop and look closely is privacy. Dusk doesn’t hide *all* transactions; instead, it does selective disclosure. When compliant, it can prove that the necessary information is provided, without putting every detail out on the public chain. XSC, DuskEVM, and Citadel’s identity framework together feel more grounded in real financial scenarios than just loudly calling it a privacy chain.

The Citadel 2 process has four steps: the License Provider performs an offline review and issues encrypted credentials; the user generates a zero-knowledge proof, revealing only that they hold valid credentials; after the contract verifies it, a public session is left behind; then the service decides whether to grant access. On-chain, it only proves that the session is valid—regardless of which organization trusts whom, what attributes are needed, or whether the credential has expired. The same identity material doesn’t have to be stored repeatedly across every platform; the risk shifts from data duplication to the issuer’s governance and revocation synchronization.

Before using Dusk, figure out the Gas first—you can save yourself from a few rounds of paying “error tuition.” Whether it works still depends on the transaction result, and whether value can continuously flow into DUSK requires further observation of the network’s real usage and supply rhythm. #dusk $DUSK

I’ve been watching @Dusk lately, and the more I look at it, the more interesting it feels.

First, let me talk about the transaction lifecycle that really hooked me. At the beginning, I was also misled by the idea of deterministic finality. I spent days reading docs before I realized that “confirmed” and “finalized” are completely different. If a block hasn’t reached the last step, it can still revert. The process goes like this: a provisioner first proposes a candidate block, then a random committee validates it, then a second set of ratifications comes in—only after ratification is it actually settled. It’s not that once it’s proposed you’re doomed, but after it’s finalized you no longer need to keep stacking confirmation counts.

If it’s just a normal transfer, fine—but with exchange deposits or securities settlement, you can’t play like this. Hearing “executed” only means it executed; you still have to confirm the error field is empty. Only the “finalized” event counts as solid. If you receive a “reverted,” then you have to listen again. A contract revert is a code error, while a block revert means consensus changed—those two recovery logics are totally different directions. If an integration party treats “confirmed” as “final,” deterministic finality can fail at the application layer. What I care about most right now is whether exchanges and Dusk Trade both use “finalized” as the boundary, and whether there’s an auditable replay process.

Next, let’s talk about fair trading—this genuinely made me sick. The mempool is like a glass room with no curtains: whatever you want to buy is visible to the entire network, and clipper/robot traders can pounce at any time. $DUSK enables private batch auctions directly at the protocol layer: the bid and quantity are submitted in a way that gets sealed with ZK instantly. Nodes then compute a fair price by estimating that the gap between hidden total buy demand and total sell supply is close to zero; then within the same block, all listed orders settle at that price. Information asymmetry gets exposed—fairness isn’t just on the surface; it’s fair at its core.

Compliance is also not being handled loosely. Phoenix uses ZK for privacy, Moonlight uses a transparent ledger, Citadel supports selective disclosure, and XSC writes credentials, restrictions, and reports directly into contract logic. You shouldn’t have to rely on rules outside the chain.

The more complex the product gets, the more rules there are. Whether it can run reliably together across all kinds of workflows is the part I’ll keep watching. Real finality isn’t a buzzword: it’s when node events propagate to the ledger without anyone racing ahead in the middle. #dusk $DUSK

Last night I went through the documents for @Dusk again, and to be honest, it made me feel a bit conflicted.

On one hand, they say they’re in the privacy space. Phoenix’s UTXO-based setup with zero-knowledge proofs is indeed hardcore, and the transfer information is tightly sealed. But then they turn around and do a DuskEVM-compatible Solidity layer, clearly aiming to capture Ethereum developer traffic. Even the official documentation says that the account model and UTXO are fundamentally not the same “species” when it comes to privacy. Full compatibility means sacrificing anonymity. So it’s awkward: building with EVM tooling is very smooth, but privacy is left half-baked. If you really want auditable privacy, you then have to bite into the threshold of the native environment—which makes it genuinely uncomfortable sitting in the middle.

The node side is even more tangled. Under the Succinct Attestation consensus, staking 1000 DUSK lets you serve as a Provisioner. The threshold looks quite friendly, so ordinary people can try it too. But if you look further up, the real value exit—RWA channels, NPEX licensing, and compliant identity verification—everything is held by institutions. The base layer is permissionless PoS, and the top layer is a permissioned club. In this kind of architecture, I still can’t figure out how the token captures value.

And that native issuance—its ambition is genuinely huge. It doesn’t just want to issue a token. It wants to pack the whitelist, view keys, controlled transfers, and settlement delivery into a single state machine. In an ideal world, private placement securities wouldn’t need off-chain ledgers. But the problem is legal enforceability and custodial recognition—no matter how elegantly it runs on-chain, it can’t replace those things.

To be frank, Phoenix’s selective disclosure, Moonlight’s dual-model switching, and Citadel’s certificate issuance logic are indeed cleverly designed. But in actual user experience, the complexity isn’t low, and regular users will likely be discouraged. I’ll admit that there’s room for the compliance narrative under Europe’s MiCA, but whether the technical advantages can translate into on-chain vitality still depends on whether the ecosystem can truly get running.

I’ll keep watching, but before real money goes in, these thorny logics have to be straightened out first. #dusk $DUSK

After running tests for half a year, I’ve gotten used to first digging into the propagation layer for blockchains. I hit a trap recently: the node’s bandwidth suddenly maxed out, and the alert emails filled up an entire screen. At first I thought it was because the transaction volume spiked too hard—after digging through the logs I realized the underlying default behavior is that the whole network keeps getting a full broadcast “drip feed.” Once the node jitters a bit, repeated messages get pushed through relentlessly, like traffic jams.

Later I looked through document @Dusk and found the Kadcast section—I really paused there for a while. It doesn’t use blind flooding. Instead, it builds on the Kademlia topology: it uses the XOR distance computed from the hash of node identity, and groups peers into different routing buckets. When broadcasting, it no longer sprays packets indiscriminately; it pushes messages in an ordered, distance-layered way, turning full-network synchronization into a structured multicast tree. In my local tests, the bandwidth peak was clearly suppressed, and after messages go through multiple hops, it becomes much harder for outsiders to infer the initiator purely from traffic patterns. The whitepaper claims it saves 25%–50% bandwidth compared to traditional Gossip—I’ll treat that as a reference. In practice, though, when nodes frequently go online and offline, jitter across regions, and routing table refresh lags, all of that stacks together, so the actual savings will almost certainly be discounted. Pairing with BitVM3 as a verification fallback means there’s no chance to get into the door for non-compliant transactions either. The underlying idea is similar to the staking-layer logic: bolt the rules into cryptography.

However, relying heavily on logical topology also has a cost. If you run into cross-country partitioning, or a malicious node injects dirty data into routing buckets, then when switching to alternate paths, the addressing/search cost can quickly wipe out any latency advantage. Controllable bandwidth is definitely a good thing: ordinary stakers don’t need to rent dedicated lines, and the threshold drops a notch. But troubleshooting is more complex than with traditional broadcasting, so you need to have it in mind.

I also stepped into a pit with cross-chain. Moving from the mainnet to BSC isn’t a simple “move.” You have to transfer the native DUSK to the official bridge account. After the mainnet locks the verification, you generate a BEP20 token according to the BSC address specified in the Memo. The amount must be greater than 1 DUSK. The fee is the mainnet transaction fee plus a 1 DUSK bridge fee. It usually takes about an hour to arrive; in reality, the received amount is the sent amount minus 1.

Kadcast uses mathematical distance to mitigate redundancy and provenance-reconstruction risks, but in the public-network environment where nodes come and go, whether routing table updates are fast enough and whether the alternate pool is thick enough—that’s the real thing you need to watch. If it runs smoothly, it’s a pragmatic upgrade; if it doesn’t, it’s just a paper façade. $DUSK #dusk $DUSK

I’ve been keeping an eye on RWA lately—honestly, the more I watch it, the more anxious I get. On the asset tokenization on-chain front, there’s no shortage of technical solutions: one idea leads to another. But the moment you ask institutions to actually move real-world assets—houses, bonds, stocks—onto a public blockchain, try it out and see. Public chains are as transparent as glass houses; every business secret is laid bare. Who would dare? Meanwhile, privacy chains are so opaque that regulators can’t even get close to the door. I looked around and found that @Dusk hasn’t taken sides—directly baking privacy and compliance into the underlying layer. That approach is kind of interesting.

I went digging into its tech stack on purpose. The Succinct Attestation consensus runs with a random committee doing the work; fork rollbacks are basically a non-starter. DuskEVM is Ethereum-compatible—I ran a small demo with Solidity, and the privacy features were included right out of the box. The Hedger protocol’s auditable privacy left me staring for a while: everything is locked down in terms of details, yet when it comes to compliance, it can produce verifiable proofs. That trick is pretty brilliant. Moonlight and Phoenix provide two transaction models in parallel—different needs, different options. I also checked the NPEX plan to tokenize more than 300 million euros in securities onto the chain; I’ll have to watch how they roll it out.

But honestly, there’s one question that keeps hanging over me: who ultimately holds the key that can unlock all privacy? That directly determines whether it’s truly freedom—or just another form of control. I did some back-of-the-envelope math: continuous token issuance and the token-locking structure suppress momentum; if EU regulation shifts, the narrative could get completely washed away. The secondary liquidity of the first batch of assets and the ZK costs still have to be validated in practice.

Recently, a lot of people were fooled by claims of 2.8 ms on-chain verification—I almost believed it too. PLONK does push verification to the limit, but that’s “light on-chain, heavy off-chain.” I ran Citadel identity circuits locally: with a single license you get over 30,000 constraints, the prover took a full 16 seconds, while the verifier only needed 0.007 seconds. The computational overhead of ZK is roughly ten thousand times the cost of the original computation—the pressure is basically dumped onto local devices.

I’m the type who likes to verify things myself; I don’t look at the head and judge from the code’s reputation. Dusk’s path is hard but correct—yet getting from technology to real-world deployment still depends on regulatory battles and market acceptance. For now, my focus is just two things: how the key is managed, and the real transaction volume after tokenizing 300 million euros’ worth of assets on-chain. As for everything else, I’ll wait until I finish running the tests before talking. #dusk $DUSK