#dusk $DUSK @Dusk spent the afternoon poking around Dusk Connect and the new wallet flow for a CreatorPad task on Dusk.. one thing kept nagging at me after.
Pulled up the wallet's provider api docs repo last touched Aug 7 and noticed the gas defaults are split by transfer type public/Moonlight transfers get the lower default price, shielded/Phoenix ones get the higher one. Small line in a markdown file. Big tell.
Because that's the actual default path through the new wallet flow connect, sign, send and the path of least resistance is the transparent one. Privacy is there, it's real, it works. But it's the deliberate extra click, not the resting state.
Kind of funny given how hard the branding leans privacy first.
In practice the UX, and the fee math underneath it, quietly rewards going public. Makes sense economically, obfuscated txs cost more to prove… but it means most people clicking through Connect for the first time probably aren't shielding anything. Not because they don't want to. Just because the default nudged them elsewhere.
grabbed my snack mid testing and just sat with that for a minute, honestly.... not knocking it, just noticing it. does privacy by default mean much if the wallet's own defaults quietly default you out of it?
$RE $HEMI
Pulled up the wallet's provider api docs repo last touched Aug 7 and noticed the gas defaults are split by transfer type public/Moonlight transfers get the lower default price, shielded/Phoenix ones get the higher one. Small line in a markdown file. Big tell.
Because that's the actual default path through the new wallet flow connect, sign, send and the path of least resistance is the transparent one. Privacy is there, it's real, it works. But it's the deliberate extra click, not the resting state.
Kind of funny given how hard the branding leans privacy first.
In practice the UX, and the fee math underneath it, quietly rewards going public. Makes sense economically, obfuscated txs cost more to prove… but it means most people clicking through Connect for the first time probably aren't shielding anything. Not because they don't want to. Just because the default nudged them elsewhere.
grabbed my snack mid testing and just sat with that for a minute, honestly.... not knocking it, just noticing it. does privacy by default mean much if the wallet's own defaults quietly default you out of it?
$RE $HEMI
