Recently, I keep getting asked whether Binance’s newly launched bStocks and Dusk are basically doing the same thing. At first, I was also a bit confused. I thought, aren’t they both just moving traditional assets onto the chain? But after comparing the two sides’ documentation line by line, I finally understood: they’re not even competing for the same “lane.” Instead, they’re more like a front-and-back relationship.
I tested bStocks by simulating trades. The logic is indeed straightforward. With U, you can buy fractional shares of Apple and Tesla, settle instantly, and you don’t need a U.S. stock account. For retail users, the experience is genuinely great—every on-chain transaction is visible, so it feels reassuring. But the problem is precisely this “visibility.” If you let institutions spread their positions and strategies entirely on-chain, what’s the difference from running around in the nude? In traditional finance, position-level details are even more sensitive than someone’s life. If I were a fund manager, I’d never, ever want the counterparty to be able to watch my cards.
Dusk takes a different approach. It uses ZK for privacy, but it’s not a fully opaque black box. Positions are hidden from the public, while regulatory nodes can still “pierce through” to perform checks. I’d only seen this kind of “auditable privacy” in papers before—there aren’t many who really dare to implement it. Also, it has clearly connected with the licensed Dutch exchange NPEX. In other words, it’s obviously aiming at compliance. Put simply, bStocks solves the question of “whether it’s possible,” while Dusk solves “whether you dare to do it.”
So when I look at these two, I don’t see them as rivals—they’re a puzzle. bStocks brings liquidity and assets onto the chain first, and handles user education. Then Dusk delivers an “invisibility cloak” to institutions, making them feel comfortable enough to move real funds onto the system. One lays the road, the other builds the walls. Without either, no RWA effort can go far. Of course, before the mainnet truly runs, all of this is still scenario planning. Whether the balance between privacy and compliance can hold up under real-world pressure—and whether the developer ecosystem can really take off—still needs continued close attention. But I think the direction is right: for RWA to succeed, it can’t rely only on retail hype. Institutions have to feel safe, compliant, and secure at the core.
#dusk $DUSK @Dusk
I tested bStocks by simulating trades. The logic is indeed straightforward. With U, you can buy fractional shares of Apple and Tesla, settle instantly, and you don’t need a U.S. stock account. For retail users, the experience is genuinely great—every on-chain transaction is visible, so it feels reassuring. But the problem is precisely this “visibility.” If you let institutions spread their positions and strategies entirely on-chain, what’s the difference from running around in the nude? In traditional finance, position-level details are even more sensitive than someone’s life. If I were a fund manager, I’d never, ever want the counterparty to be able to watch my cards.
Dusk takes a different approach. It uses ZK for privacy, but it’s not a fully opaque black box. Positions are hidden from the public, while regulatory nodes can still “pierce through” to perform checks. I’d only seen this kind of “auditable privacy” in papers before—there aren’t many who really dare to implement it. Also, it has clearly connected with the licensed Dutch exchange NPEX. In other words, it’s obviously aiming at compliance. Put simply, bStocks solves the question of “whether it’s possible,” while Dusk solves “whether you dare to do it.”
So when I look at these two, I don’t see them as rivals—they’re a puzzle. bStocks brings liquidity and assets onto the chain first, and handles user education. Then Dusk delivers an “invisibility cloak” to institutions, making them feel comfortable enough to move real funds onto the system. One lays the road, the other builds the walls. Without either, no RWA effort can go far. Of course, before the mainnet truly runs, all of this is still scenario planning. Whether the balance between privacy and compliance can hold up under real-world pressure—and whether the developer ecosystem can really take off—still needs continued close attention. But I think the direction is right: for RWA to succeed, it can’t rely only on retail hype. Institutions have to feel safe, compliant, and secure at the core.
#dusk $DUSK @Dusk