Spent an hour poking around DuskEVM testnet transactions today, and the thing that stuck wasn't the tech, it was the default wallet flow. Dusk Network ($DUSK , #dusk , @Dusk ) markets itself as the privacy-first chain for regulated finance, but spinning up a new wallet drops you straight into a transparent EVM-compatible address, visible balances, visible transfers, nothing shielded. Phoenix, the actual privacy-preserving transaction model, sits one layer deeper, something you opt into rather than something you start with. So the chain that's supposed to make confidentiality the baseline actually ships confidentiality as an extra step, while transparency is what a new user touches first. It's a small design choice, but it inverts the pitch: institutions get promised discretion, but the first experience anyone has on the network is the opposite of that. Maybe that's just sequencing, onboarding simplicity before advanced features. Or maybe it says something about which use case the chain is actually optimized for right now. Still not sure which.