#dusk I have been looking at Dusk’s privacy model again and the recent network changes make it more interesting than just a privacy feature.Dusk separates public and private transaction flows.
Moonlight keeps balances and transfers visible, while Phoenix was designed around shielded notes and zero knowledge proofs. The private side hides transaction amounts and key details while still allowing the network to verify that the transfer is valid.
The June Boreas upgrade retired Phoenix transactions on mainnet, while the broader architecture is moving toward confidential flows through DuskEVM and Hedger.
Hedger uses encrypted values and zero knowledge proofs to bring confidential transfers into the EVM environment. That matters because Dusk is trying to connect privacy with actual regulated asset workflows instead of keeping it isolated at the protocol level.
The latest Dusk discussion around tokenized private markets also keeps coming back to confidential transactions and selective disclosure. Feels quiet lately, but something is building maybe.
@Dusk
$DUSK
Moonlight keeps balances and transfers visible, while Phoenix was designed around shielded notes and zero knowledge proofs. The private side hides transaction amounts and key details while still allowing the network to verify that the transfer is valid.
The June Boreas upgrade retired Phoenix transactions on mainnet, while the broader architecture is moving toward confidential flows through DuskEVM and Hedger.
Hedger uses encrypted values and zero knowledge proofs to bring confidential transfers into the EVM environment. That matters because Dusk is trying to connect privacy with actual regulated asset workflows instead of keeping it isolated at the protocol level.
The latest Dusk discussion around tokenized private markets also keeps coming back to confidential transactions and selective disclosure. Feels quiet lately, but something is building maybe.
@Dusk
$DUSK