I started paying attention to DuskEVM when the testnet launched on 10/8. What I found valuable is that developers don’t need to give up what they already know: Solidity, Hardhat, and Ethereum tools are still usable on @Dusk
My first impression: “Pretty interesting—the NPEX execution layer is no longer just on paper!”
I had to slow myself down. Developer access is open, but that isn’t proof of adoption yet. There are no contracts, no volume, or activity to show the system is moving. The door is open, but the hallway behind it is still quiet.
I had to recalibrate how I view NPEX. Hearing that €300M in securities have been tokenized, the natural reflex is to assume they’re already on-chain and being used. But the closer I look, the clearer the gap becomes: the infrastructure for those transactions was only opened to developers last week.
That isn’t impressive, but I like it. It makes me view NPEX more realistically: it currently has the capability to build, but there’s no evidence of activity yet. Having infrastructure doesn’t mean applications have appeared, and it certainly doesn’t mean users need it.
I understand why they’re doing this. If the goal is a system for institutions and regulatory bodies, building the infrastructure first and waiting for volume to come is a pretty sensible order for me.
Actually, I’m a bit ahead of the chain’s timeline. This is a familiar mistake for anyone following a project: you see “partners already exist” and then turn it into “partners are already using it.” But those two things can be different.
Now I’m curious about how fast this is going. Do developers mess around in the DuskEVM sandbox and generate activity, or will the testnet sit idle for a few months?
To be honest, I don’t have an answer yet.
I’m curious whether the first developers have already stepped into DuskEVM. Or is the sandbox still waiting for activity?
That’s the most I’ll pay attention to in the coming time!#dusk $DUSK $AKE