Dusk is holding a community AMA later today, which feels like the right moment to share the checklist I've built after two weeks of researching this project. Not what I hope happens — what would need to happen.

First, the NPEX deployment has to graduate from partnership to production. A licensed venue actively issuing and trading tokenized securities on #dusk rails would be the strongest validation available, because it's verifiable rather than promised.

Second, DuskEVM has to convert developer curiosity into shipped applications. Familiar tooling plus confidential execution is a genuinely differentiated pitch — but only if builders actually use it. Tools like the recent Dusk Connect SDK suggest the team understands this.

Third, more regulated entities have to follow the first one. Institutions move in herds; the second and third licensed adopters matter more than the tenth press release.

Fourth, European regulation has to keep rewarding compliance-first design.

And underneath everything: execution. Roadmaps slip in this industry, and honest projects acknowledge that.

Notice none of my checklist involves price. Infrastructure either gets used or it doesn't.

What would be on your checklist?

I'm curious what others are watching.
@Dusk $DUSK $BEAT