I Followed The Sentence That Points Somewhere Else
@Dusk
Documentation reveals priorities through its routing. Which page tells you to keep reading, and which one quietly hands you to a different product, says more than any feature list.
#dusk does this on the DuskDS transaction models deep dive. It explains Phoenix in detail, then adds that if you are building dApps on DuskEVM, you'll mostly interact with Hedger and EVM contracts instead. The same page introduces DuskEVM as the EVM execution layer where smart contracts run and where Hedger lives.
Phoenix is the stronger primitive. The page says it proves a transfer without revealing how much is moving, who sent the note except to the receiver, and between which specific notes.
Hedger operates under a different constraint, and Dusk states it plainly in the June 2025 launch post. The EVM's account based model prevents full anonymity, a capability Zedger still offers.
That last clause is what I keep returning to. Zedger is the L1 protocol for regulated assets, and it never shipped. A team hangout in September 2025 described the specification as complete, with a minimum viable product that hasn't been fully tested, after development priorities shifted elsewhere.
Everything regulated points the other way regardless. The NPEX dApp runs on DuskEVM. Dusk Trade sits on DuskEVM. The Chainlink deal makes composable the assets issued on DuskEVM.
The honest part is that full sender anonymity was probably never usable at a licensed venue. An operator has to know who is trading. MiFID II hides counterparty identity from the market, not from the venue.
So the stronger model cannot serve regulated flows, and the alternative Dusk names in its own concession was never built.
Which leaves me unsure what the L1 privacy was being held in reserve for.$DUSK
@Dusk
Documentation reveals priorities through its routing. Which page tells you to keep reading, and which one quietly hands you to a different product, says more than any feature list.
#dusk does this on the DuskDS transaction models deep dive. It explains Phoenix in detail, then adds that if you are building dApps on DuskEVM, you'll mostly interact with Hedger and EVM contracts instead. The same page introduces DuskEVM as the EVM execution layer where smart contracts run and where Hedger lives.
Phoenix is the stronger primitive. The page says it proves a transfer without revealing how much is moving, who sent the note except to the receiver, and between which specific notes.
Hedger operates under a different constraint, and Dusk states it plainly in the June 2025 launch post. The EVM's account based model prevents full anonymity, a capability Zedger still offers.
That last clause is what I keep returning to. Zedger is the L1 protocol for regulated assets, and it never shipped. A team hangout in September 2025 described the specification as complete, with a minimum viable product that hasn't been fully tested, after development priorities shifted elsewhere.
Everything regulated points the other way regardless. The NPEX dApp runs on DuskEVM. Dusk Trade sits on DuskEVM. The Chainlink deal makes composable the assets issued on DuskEVM.
The honest part is that full sender anonymity was probably never usable at a licensed venue. An operator has to know who is trading. MiFID II hides counterparty identity from the market, not from the venue.
So the stronger model cannot serve regulated flows, and the alternative Dusk names in its own concession was never built.
Which leaves me unsure what the L1 privacy was being held in reserve for.$DUSK
