#dusk Two privacy systems exist on Dusk right now not one and that split rarely gets mentioned when people describe the network as simply privacy focused.
Phoenix runs natively on DuskDS UTXO-based nullifier-driven the model this entire network was originally built around. Hedger runs separately on DuskEVM built on homomorphic encryption paired with zero-knowledge proofs engineered specifically for what the documentation calls reviewable privacy in regulated finance.
Different execution-layers needed different tools. Phoenix’s mechanics were never built for an EVM-context so DuskEVM got its own privacy module instead of inheriting Phoenix’s.
That reasoning holds up. What it also means two separate security assumptions two separate audit-surfaces two separate cryptographic models a builder has to actually understand correctly rather than one unified privacy layer covering the entire network.
Neither system is weaker for existing separately. But Dusk has privacy is doing a lot of quiet work in that sentence covering two genuinely different answers to what privacy actually means depending on which layer you’re building on.$DUSK
@Dusk_Foundation @Dusk
#dusk
Which mitigation matters most here?
Phoenix runs natively on DuskDS UTXO-based nullifier-driven the model this entire network was originally built around. Hedger runs separately on DuskEVM built on homomorphic encryption paired with zero-knowledge proofs engineered specifically for what the documentation calls reviewable privacy in regulated finance.
Different execution-layers needed different tools. Phoenix’s mechanics were never built for an EVM-context so DuskEVM got its own privacy module instead of inheriting Phoenix’s.
That reasoning holds up. What it also means two separate security assumptions two separate audit-surfaces two separate cryptographic models a builder has to actually understand correctly rather than one unified privacy layer covering the entire network.
Neither system is weaker for existing separately. But Dusk has privacy is doing a lot of quiet work in that sentence covering two genuinely different answers to what privacy actually means depending on which layer you’re building on.$DUSK
@Dusk_Foundation @Dusk
#dusk
Which mitigation matters most here?
Iteration cap
50%
Generator payout rules
0%
Next-gen exclusion
50%
Iteration cap
0%
2 Stimmen • Abstimmung beendet