Just got off a DuskEVM testnet run and honestly the thing that stuck was smaller than I expected.
Dusk ($DUSK ) rolled DuskEVM testnet live on Aug 10 — full Solidity/Hardhat compatibility, OP Stack under the hood. I deployed a basic contract during the task, verified it through the testnet Blockscout explorer per the quickstart docs... and there it was. Deployer address, balance, contract bytecode, every call — sitting in plain view, same as any other EVM chain. #dusk @Dusk
Here's the part that made me pause. Dusk markets itself hard on "privacy with selective disclosure," confidential by default, ZK everywhere. But that's the native L1. DuskEVM — the part institutions actually plug Solidity apps into — ships transparent by default. Privacy isn't baked into the account model here, it's routed through Hedger, a separate testnet product bolted on top with homomorphic encryption. Two different products, two different trust assumptions, and most people reading "secured by Dusk" won't clock which one they're actually building on.
Kept refreshing the explorer like it'd change. It didn't.
Not saying that's bad design necessarily — modularity has its logic. But if account-level privacy is the pitch for institutional EVM apps, and the EVM layer itself doesn't have it natively... who's actually opting into Hedger once mainnet goes live, versus just shipping public and calling it compliant?
#dusk
Dusk ($DUSK ) rolled DuskEVM testnet live on Aug 10 — full Solidity/Hardhat compatibility, OP Stack under the hood. I deployed a basic contract during the task, verified it through the testnet Blockscout explorer per the quickstart docs... and there it was. Deployer address, balance, contract bytecode, every call — sitting in plain view, same as any other EVM chain. #dusk @Dusk
Here's the part that made me pause. Dusk markets itself hard on "privacy with selective disclosure," confidential by default, ZK everywhere. But that's the native L1. DuskEVM — the part institutions actually plug Solidity apps into — ships transparent by default. Privacy isn't baked into the account model here, it's routed through Hedger, a separate testnet product bolted on top with homomorphic encryption. Two different products, two different trust assumptions, and most people reading "secured by Dusk" won't clock which one they're actually building on.
Kept refreshing the explorer like it'd change. It didn't.
Not saying that's bad design necessarily — modularity has its logic. But if account-level privacy is the pitch for institutional EVM apps, and the EVM layer itself doesn't have it natively... who's actually opting into Hedger once mainnet goes live, versus just shipping public and calling it compliant?
#dusk