#dusk @Dusk Here's something small in the Dusk docs that I actually found elegant.
A Dusk profile pairs a Moonlight account with a Phoenix account derived from the same mnemonic.
So instead of thinking:
public wallet over here
private wallet over there
the wallet can manage both transaction models together.
That is a subtle UX decision with a bigger architectural consequence.
Moonlight exposes public account activity.
Phoenix works with shielded notes.
They're fundamentally different ways of representing value, yet the user shouldn't necessarily have to think of them as two completely unrelated financial identities.
That separation between underlying mechanics and user mental model is important.
The protocol can remain sophisticated underneath while the wallet presents a coherent account experience.
And there's another interesting implication.
If a single profile can organise both sides, switching between transparent and shielded activity becomes a wallet-level decision rather than requiring the user to maintain an entirely separate identity system.
That feels much closer to how real financial users think.
They don't wake up thinking:
“Today I will use transaction model A.”
They think:
“I need to send this payment.”
The infrastructure decides what machinery is appropriate.
Small feature.
Big UX lesson.
$DUSK