Dusk Network works like a two-layer machine: fast settlement underneath, flexible apps on top.
Today I’m looking at how #Dusk Network actually moves value behind the scenes, because the design explains the whole vision. First, the base layer is DuskDS, which handles consensus, settlement, data availability, and the transaction models that make privacy possible. On top of that sits DuskEVM, where developers can use familiar EVM tooling while still tapping into Dusk’s privacy and compliance primitives when they need them.
When a transfer happens, the privacy logic isn’t “added later.” It’s built into how transactions are formed and validated. Phoenix is the transaction model designed for privacy-preserving transfers and confidential activity, so the chain can confirm correctness without exposing every detail to the public.
Then, for regulated instruments and security-token style logic, Dusk Network extends the model with Zedger, so you can get account-like behavior for contracts without throwing privacy away. That’s where XSC comes in: a standard aimed at issuing and managing privacy-enabled tokenized securities with compliance-aware rules.
