I kept thinking about how easily “better UX” can hide a change in user behavior. At first, Dusk Connect looked like another wallet-connect layer. But the deeper I looked, the more interesting the friction became. Dusk opened Connect and its new Wallet for developer preview on April 22, supporting public/private transfers, shield/unshield flows and per-origin dApp permissions. That matters because the interface isn’t just exposing privacy; it is shaping how users encounter it. Making shielded activity easier is useful, but capability alone doesn’t create a habit. Will users keep choosing shielded transfers once the novelty disappears, or does privacy need to become the path of least resistance before it becomes something people actually use by default?

@Dusk $DUSK #dusk