Dusk is building three paths: Native, EVM and confidential EVM.
What I find interesting is the practical choice this creates. You can stay on the native side, move into EVM, or use the confidential EVM path when privacy becomes the priority.
While testing the different pieces, the thing I kept coming back to was friction. Supporting three paths sounds useful, but it also means developers have to decide where their application actually belongs instead of treating Dusk as one simple execution environment.
The numbers make the direction clearer. Dusk has *10,000+ transactions per second* as a stated target, while its EVM work is aimed at making existing Ethereum tooling usable without forcing everything into a new development stack.
That sounds good on paper. But I’m more interested in what happens when an application starts moving between these paths.
Does the EVM route become the default because it is familiar? Does confidential EVM actually pull applications toward privacy-sensitive use cases? Or does Native remain the place where the deeper advantages are easiest to capture?
Three paths give developers more options, but they also create a new decision point.
That trade-off is probably going to matter more than the headline numbers as real applications start choosing where to live...
#dusk $DUSK @Dusk
What I find interesting is the practical choice this creates. You can stay on the native side, move into EVM, or use the confidential EVM path when privacy becomes the priority.
While testing the different pieces, the thing I kept coming back to was friction. Supporting three paths sounds useful, but it also means developers have to decide where their application actually belongs instead of treating Dusk as one simple execution environment.
The numbers make the direction clearer. Dusk has *10,000+ transactions per second* as a stated target, while its EVM work is aimed at making existing Ethereum tooling usable without forcing everything into a new development stack.
That sounds good on paper. But I’m more interested in what happens when an application starts moving between these paths.
Does the EVM route become the default because it is familiar? Does confidential EVM actually pull applications toward privacy-sensitive use cases? Or does Native remain the place where the deeper advantages are easiest to capture?
Three paths give developers more options, but they also create a new decision point.
That trade-off is probably going to matter more than the headline numbers as real applications start choosing where to live...
#dusk $DUSK @Dusk