When it comes to privacy and transparency, many people fall into a dead end: either completely anonymous and untraceable, or fully open and lacking security. But in fact, this is a false dilemma.

The Dusk project has had a different approach from the very beginning. It doesn't choose extremes but finds a delicate balance between privacy and accountability.

So how does it work? The core logic is this: sensitive information is locked by default, but the system leaves a "permissioned access" door open.

Once the Phoenix protocol goes live on the mainnet on January 7, 2026, this mechanism will truly come into operation. Every on-chain interaction—sender, receiver, transaction details—are wrapped with zero-knowledge proofs. Outsiders see only a meaningless string of mathematical proof—information definitely existed, but the specific content can never be reconstructed.

Authorized parties? They can quickly generate verification proofs through a set of cryptographic steps. These proofs answer only four questions: Is it compliant? Did it occur? Is the amount correct? Does the source match? But they never reveal the original data.

In other words, the proof attests to the conclusion, not the process.

The underlying idea is very practical: complete hiding loses accountability, while full transparency destroys security and competitiveness. Real-world privacy needs are never black-and-white.

The Citadel protocol continues this approach, returning identity control to the user—certificates are self-held, information is disclosed minimally as needed, and proof generation is entirely user-driven. After the mainnet launches, this logic has already been running on real nodes, and developers can directly build applications based on these primitives.