#dusk $DUSK @Dusk Something small kept coming back to me after I read Dusk's latest progress update.
Buried in a list of safeguards was one line: Phoenix transfers that move value are now obfuscated by default. Per Dusk's own update from July 2026, this landed as part of a broader hardening pass on how private transactions get created, validated, and handled by wallets.

I sat with that phrase, obfuscated by default, longer than the rest of the update. The word "now" is doing a lot of work there, and I find myself wondering what it's quietly contrasting against.
That matters more in a system built for financial applications than it would elsewhere. A wallet doing something as ordinary as sending funds shouldn't depend on the sender getting a setting right. Default behavior is what most people actually experience.

The update also mentions this change is bound for an upcoming network upgrade, alongside stricter rejection of malformed transaction data. What I can't tell yet is what the update is comparing this "default" state to, or whether that's even the right question to be asking.