so i went down a rabbit hole on node types today instead of doing what i was meant to be doing 😂
theres three. provisioner, archive, prover. provisioners are the ones in consensus, they propose validate and ratify, and staking DUSK is how you get into that set. archive nodes keep history. prover nodes do the proving work.
what got me is that provisioner selection is random per round. your not permanently on a committee, your drawn into one. so a big staker isnt sitting there deciding blocks continuously, theyre just drawn more often.
theres also a whole slashing recovery guide in the operator docs wich tells you something. you dont write recovery documentation for a thing that never happens. slashing is real and people hit it, probably mostly through downtime rather then anything malicious.
i was going to look at the hardware requirments too but got distracted reading the troubleshooting page instead, wich is weirdly the most honest page in any docs, its just a list of everything that goes wrong.
staking basics is under Manage DUSK if anyones actually thinking about running one.
#dusk @Dusk $DUSK
theres three. provisioner, archive, prover. provisioners are the ones in consensus, they propose validate and ratify, and staking DUSK is how you get into that set. archive nodes keep history. prover nodes do the proving work.
what got me is that provisioner selection is random per round. your not permanently on a committee, your drawn into one. so a big staker isnt sitting there deciding blocks continuously, theyre just drawn more often.
theres also a whole slashing recovery guide in the operator docs wich tells you something. you dont write recovery documentation for a thing that never happens. slashing is real and people hit it, probably mostly through downtime rather then anything malicious.
i was going to look at the hardware requirments too but got distracted reading the troubleshooting page instead, wich is weirdly the most honest page in any docs, its just a list of everything that goes wrong.
staking basics is under Manage DUSK if anyones actually thinking about running one.
#dusk @Dusk $DUSK
