At first I assumed Dusk Connect was just another wallet-connect clone, a button that opens a modal and calls it dApp support. But the details filter for something more specific. Default gas presets sit lower for public transfers and higher for shielded ones, so the wallet nudges behavior before a user consciously chooses. That's not neutral plumbing. It's friction placed exactly where habits get set.
The new Dusk Wallet follows the same logic. A dApp can query what's supported before any connection permission exists, so discovery happens ahead of trust rather than alongside it. Convenient, yes, but it also reshapes what "connecting" actually means for the user on the other end. None of this proves adoption. Reducing friction can just as easily reduce memorability. The real question isn't whether shielded transfers work. It's whether anyone keeps choosing them once the default wears off, or whether privacy ends up as a setting people enable once and never touch again.
@Dusk $DUSK #dusk
The new Dusk Wallet follows the same logic. A dApp can query what's supported before any connection permission exists, so discovery happens ahead of trust rather than alongside it. Convenient, yes, but it also reshapes what "connecting" actually means for the user on the other end. None of this proves adoption. Reducing friction can just as easily reduce memorability. The real question isn't whether shielded transfers work. It's whether anyone keeps choosing them once the default wears off, or whether privacy ends up as a setting people enable once and never touch again.
@Dusk $DUSK #dusk
