i went to check how duskevm actually orders transactions, since rollups built on op stack usually get judged by how decentralized their sequencer setup is. dusk's own docs say it plainly — duskevm currently has no public mempool, sequencer only, and i actually went back and reread that line assuming i'd misunderstood "sequencer only" as just meaning "no third-party relayers," it means no public mempool at all, full stop.
that means right now, one party controls transaction ordering and inclusion timing on that whole layer. it's not unusual for a new op stack rollup, most launch this way and decentralize the sequencer later, but it's also not a small detail for a chain positioning itself around institutional trust and deterministic settlement. a private mempool is exactly the kind of thing that lets front-running or selective ordering happen without anyone external being able to verify it isn't.
what's actually interesting is the pairing — hedger exists specifically to add confidential transaction flows on top of duskevm, but if the sequencer itself can see and order everything before anything reaches DuskDS, the privacy guarantee and the ordering guarantee are sitting in two completely different places, one cryptographic, one just trust-based.
is there a published timeline anywhere for when the duskevm sequencer actually decentralizes? 🧐

#dusk $DUSK @Dusk