I assumed participating in Dusk meant downloading one binary and calling it a day.
Sync, validate, earn.
That sounds like the usual node-operator playbook.

Then I opened the node docs and realized Dusk's operator docs separate infrastructure into three node roles.
Provisioners participate in consensus, including block generation and committee duties.
Archives retain finalized historical indexes for historical queries. Provers handle the computation-heavy task of generating Zero-Knowledge proofs.

Same network. Three completely different jobs.

The architecture separates these responsibilities.
The separation of responsibilities can reduce overlap between roles.

But here's the friction.
Dusk's own documentation also shows that these roles can overlap: a provisioner can include proving, and an archive node can participate in consensus.
Dusk makes you think about which node role matches the job you want to perform.
What looks like clean separation on paper can feel like overhead in practice.

Does specialization make the network more robust, or just make running it a part-time job?

#dusk $DUSK @Dusk
$PROM $UAI