#dusk $DUSK
The Line In The Duskevm Docs I Keep Going Back To
@Dusk
Rollup marketing usually talks about settlement, while the thing users actually experience is ordering. Different components handle each, and in most designs only one of them is decentralized.
Dusk (@DuskFoundation) puts both claims within a few clicks of each other. The homepage says DuskEVM gives a familiar EVM path to regulated market applications that need stronger settlement guarantees. The developer docs say DuskEVM currently has no public mempool, sequencer only.
The lifecycle page is careful about the rest. It walks through submission to the sequencer, the batcher publishing transaction data to DuskDS, state commitments and fault proofs connecting the result to settlement, and then warns that inclusion and settlement are different stages. Applications are told to read protocol status rather than infer finality from elapsed time. That is honest engineering documentation and I want to credit it.
What I could not find is who operates the sequencer, whether more than one party ever can, or whether a user has any force inclusion path if their transaction gets dropped. I went through the docs, the roadmap posts, and the multilayer announcement. Nothing on any of it.
That gap reads differently here than on a general purpose chain. The multilayer post states that NPEX's MTF, ECSP and Broker licences apply to the full stack. Dusk Trade sits on DuskEVM. MiFID II Article 4(1)(22) defines an MTF as a system bringing together third party buying and selling interests in accordance with non-discretionary rules, and the standard reading is that the operator holds no discretion over how those interests interact.
In fairness, every major L2 still runs one sequencer in 2026. Base, Arbitrum, OP Mainnet, the same everywhere.
None of those chains sits under an MTF licence.
If a single party decides what order securities trades enter a block, where is the non-discretion?
The Line In The Duskevm Docs I Keep Going Back To
@Dusk
Rollup marketing usually talks about settlement, while the thing users actually experience is ordering. Different components handle each, and in most designs only one of them is decentralized.
Dusk (@DuskFoundation) puts both claims within a few clicks of each other. The homepage says DuskEVM gives a familiar EVM path to regulated market applications that need stronger settlement guarantees. The developer docs say DuskEVM currently has no public mempool, sequencer only.
The lifecycle page is careful about the rest. It walks through submission to the sequencer, the batcher publishing transaction data to DuskDS, state commitments and fault proofs connecting the result to settlement, and then warns that inclusion and settlement are different stages. Applications are told to read protocol status rather than infer finality from elapsed time. That is honest engineering documentation and I want to credit it.
What I could not find is who operates the sequencer, whether more than one party ever can, or whether a user has any force inclusion path if their transaction gets dropped. I went through the docs, the roadmap posts, and the multilayer announcement. Nothing on any of it.
That gap reads differently here than on a general purpose chain. The multilayer post states that NPEX's MTF, ECSP and Broker licences apply to the full stack. Dusk Trade sits on DuskEVM. MiFID II Article 4(1)(22) defines an MTF as a system bringing together third party buying and selling interests in accordance with non-discretionary rules, and the standard reading is that the operator holds no discretion over how those interests interact.
In fairness, every major L2 still runs one sequencer in 2026. Base, Arbitrum, OP Mainnet, the same everywhere.
None of those chains sits under an MTF licence.
If a single party decides what order securities trades enter a block, where is the non-discretion?
