#dusk $DUSK I was reading more about Dusk today and ended up spending more time on Zedger than I expected. I think I initially looked at privacy in a pretty simple way: either transaction details are public or they’re hidden. Zedger made that view feel a bit too basic.
What I find interesting is how Dusk approaches account information. Balance changes can stay private in the account owner’s memory, while a change to the public root can still be revealed. I’m still getting my head around the technical side of it, but I like the idea behind the separation. Privacy doesn’t necessarily have to mean that nobody can verify anything.
This makes more sense to me when I think about regulated assets. If you’re dealing with security tokens and financial activity, putting every detail in public probably isn’t practical. At the same time, making everything completely private creates its own problems when verification or compliance is needed. Dusk seems to be trying to sit somewhere between those two extremes.
I do have a question though: how well does this actually work once real institutions, compliance requirements and different users are involved? A model can make sense technically, but the real test for me is whether people can use it without creating another layer of complexity.
I’m curious to see what that looks like when the system is being used at real scale. @Dusk_Foundation
What I find interesting is how Dusk approaches account information. Balance changes can stay private in the account owner’s memory, while a change to the public root can still be revealed. I’m still getting my head around the technical side of it, but I like the idea behind the separation. Privacy doesn’t necessarily have to mean that nobody can verify anything.
This makes more sense to me when I think about regulated assets. If you’re dealing with security tokens and financial activity, putting every detail in public probably isn’t practical. At the same time, making everything completely private creates its own problems when verification or compliance is needed. Dusk seems to be trying to sit somewhere between those two extremes.
I do have a question though: how well does this actually work once real institutions, compliance requirements and different users are involved? A model can make sense technically, but the real test for me is whether people can use it without creating another layer of complexity.
I’m curious to see what that looks like when the system is being used at real scale. @Dusk_Foundation