I’ve been looking at how wallet privacy works and honestly the more I look at it the more important the wallet structure becomes. A wallet shouldn’t have to expose everything just because you need to use a public address.
That’s where @Dusk_Foundation gets interesting.
The interesting part starts with a Mnemonic based on the BIP-39 seed phrase. That becomes the wallet’s cryptographic seed and from there the same wallet can derive multiple profiles.
Each profile is built as a tuple of key pairs. Profile 1 can have its own public address and shielded address. Profile 2 can have another public address and shielded address. The same structure can continue across Profile n. $ACE
This gives the wallet a way to organize multiple profiles under the same cryptographic seed while keeping public and shielded addresses within each profile.
The real use is pretty straightforward. One profile can work with a public address while another can use a shielded address depending on what the user needs.
That’s the purpose of this design to me. It isn’t about forcing every interaction into one address type. It gives the wallet a structure where multiple profiles and different address types can exist together.
The interesting part is that this is built into the wallet architecture itself rather than being something added later.$RICE
It’s not trying to make the wallet complicated for the sake of it. The idea is simple: one cryptographic seed can support multiple profiles with public and shielded addresses.
That’s what makes Dusk’s wallet structure worth watching.
@Dusk_Foundation
#dusk $DUSK
That’s where @Dusk_Foundation gets interesting.
The interesting part starts with a Mnemonic based on the BIP-39 seed phrase. That becomes the wallet’s cryptographic seed and from there the same wallet can derive multiple profiles.
Each profile is built as a tuple of key pairs. Profile 1 can have its own public address and shielded address. Profile 2 can have another public address and shielded address. The same structure can continue across Profile n. $ACE
This gives the wallet a way to organize multiple profiles under the same cryptographic seed while keeping public and shielded addresses within each profile.
The real use is pretty straightforward. One profile can work with a public address while another can use a shielded address depending on what the user needs.
That’s the purpose of this design to me. It isn’t about forcing every interaction into one address type. It gives the wallet a structure where multiple profiles and different address types can exist together.
The interesting part is that this is built into the wallet architecture itself rather than being something added later.$RICE
It’s not trying to make the wallet complicated for the sake of it. The idea is simple: one cryptographic seed can support multiple profiles with public and shielded addresses.
That’s what makes Dusk’s wallet structure worth watching.
@Dusk_Foundation
#dusk $DUSK