#dusk One detail in Dusk’s Phoenix model makes this more interesting. Notes can be transparent or obfuscated, meaning the system can handle different levels of information visibility inside the same transaction model. In a transparent note, the value is visible. In an obfuscated note, the value is encrypted, while the note still uses Dusk’s privacy mechanism.
I think the useful idea here is flexibility. Dusk didn’t make every note equally visible because some data may need to be checked, while some should stay hidden.
There’s even a practical trade-off: Dusk made zero-value transactions transparent because keeping them obfuscated would add unnecessary entries to the note tree. That helps reduce avoidable data over time.
So the better question isn’t “private or public?” It’s what actually needs to be visible? $DUSK @Dusk
I think the useful idea here is flexibility. Dusk didn’t make every note equally visible because some data may need to be checked, while some should stay hidden.
There’s even a practical trade-off: Dusk made zero-value transactions transparent because keeping them obfuscated would add unnecessary entries to the note tree. That helps reduce avoidable data over time.
So the better question isn’t “private or public?” It’s what actually needs to be visible? $DUSK @Dusk