Two words stopped me mid-scroll on Dusk's site today: shield, unshield. I went back and reread the wallet announcement from a couple months ago, the one I'd skimmed past the first time.
I'd assumed a privacy chain would just make every transfer private by default. That's not what's happening here. The wallet supports public and private transfers, shield and unshield, and the choice sits with whoever's sending, made fresh each time, per the official announcement.
Then I caught something smaller, easy to miss. Key storage isn't uniform across platforms. Browser extension builds run on PBKDF2 and AES-GCM. Desktop and mobile builds run on Stronghold paired with Argon2, per the same release. Two distinct security models depending on where the wallet lives.
I keep circling back to what this means for the confidential contract side. If shielding is a per-transaction choice, that changes how selective disclosure actually plays out in practice, not as a protocol-level abstraction, but at the exact moment someone hits send.
One thing I can't answer yet: once a transfer is unshielded, does it stay visible permanently from that point, or is there any reversibility built in. The announcement doesn't say, and I haven't found it addressed anywhere else official.
$DUSK #dusk @Dusk #dusk $DUSK
I'd assumed a privacy chain would just make every transfer private by default. That's not what's happening here. The wallet supports public and private transfers, shield and unshield, and the choice sits with whoever's sending, made fresh each time, per the official announcement.
Then I caught something smaller, easy to miss. Key storage isn't uniform across platforms. Browser extension builds run on PBKDF2 and AES-GCM. Desktop and mobile builds run on Stronghold paired with Argon2, per the same release. Two distinct security models depending on where the wallet lives.
I keep circling back to what this means for the confidential contract side. If shielding is a per-transaction choice, that changes how selective disclosure actually plays out in practice, not as a protocol-level abstraction, but at the exact moment someone hits send.
One thing I can't answer yet: once a transfer is unshielded, does it stay visible permanently from that point, or is there any reversibility built in. The announcement doesn't say, and I haven't found it addressed anywhere else official.
$DUSK #dusk @Dusk #dusk $DUSK