The detail that made me look twice: Dusk’s privacy stack changed underneath the headline.
On June 10, 2026, the Boreas upgrade restarted mainnet at block 4,414,095 and disabled new Phoenix transactions. Dusk kept the old Phoenix decoding only so historical blocks remain replayable.
That matters because Phoenix was the native shielded transfer model most people associate with Dusk. The current architecture points elsewhere for new privacy work: Dusk now describes a native ZK/WASM path on DuskVM for confidential assets and smart contracts, while DuskEVM adds confidential flows through Hedger.
So my takeaway isn’t “Dusk dropped privacy.” It’s almost the opposite: the privacy thesis is moving up the stack, from a dedicated shielded transfer model toward programmable financial applications.
That makes the XSC story more interesting to me. Can Dusk turn that architectural shift into real confidential contract usage, rather than simply preserving privacy as a feature on paper?
@Dusk $DUSK #dusk
On June 10, 2026, the Boreas upgrade restarted mainnet at block 4,414,095 and disabled new Phoenix transactions. Dusk kept the old Phoenix decoding only so historical blocks remain replayable.
That matters because Phoenix was the native shielded transfer model most people associate with Dusk. The current architecture points elsewhere for new privacy work: Dusk now describes a native ZK/WASM path on DuskVM for confidential assets and smart contracts, while DuskEVM adds confidential flows through Hedger.
So my takeaway isn’t “Dusk dropped privacy.” It’s almost the opposite: the privacy thesis is moving up the stack, from a dedicated shielded transfer model toward programmable financial applications.
That makes the XSC story more interesting to me. Can Dusk turn that architectural shift into real confidential contract usage, rather than simply preserving privacy as a feature on paper?
@Dusk $DUSK #dusk