Wait — the thing "protecting" your DuskEVM trade from bots right now isn't even the fancy tech.
Everyone talks about Hedger, DuskEVM's ($DUSK #dusk @DuskFoundation) privacy engine — homomorphic encryption plus ZK proofs, encrypted balances, real cryptography. That's not what's stopping front-running today though.
I checked the docs. DuskEVM currently runs sequencer-only. No public mempool. One sequencer, nothing for bots to watch and jump ahead of. That's the actual mechanism.
So there are two different "privacy" stories stacked on top of each other, and it's easy to credit the wrong one. Hedger is real cryptographic privacy, audit-ready by design. Front-running protection is something else — a side effect of having one sequencer with nothing exposed.
Here's what I haven't found yet: any doc or roadmap saying whether DuskEVM's sequencer stays single or opens up over time. If it ever becomes multi-party or public, this specific protection would need something to replace it. That's not confirmed anywhere I've seen — just a question the current setup raises.
Curious if anyone's tracked DuskEVM's actual sequencer roadmap. Genuinely don't know the answer here.
@Dusk_Foundation