#dusk $DUSK While reviewing DUSK validator sets in theory 100 provisioners can look safer than 10, until the stake distribution says the opposite.
That is the part I think people miss. DUSK security is not really about validator count alone. Ten large provisioners controlling most stake can matter more than 100 small ones with little weight.
The same problem appears with Byzantine stake. Moving from 20% to 30% looks like only +10 percentage points, but it is actually 50% more adversarial capital. And 30% vs 33.3% vs 35% is not a smooth progression either. Crossing the one-third boundary changes the security condition itself.
This is why DUSK’s architecture matters. The older bid/stake/reward structure separated more moving parts, while the current Stake + Transfer model concentrates provisioners, stakes, rewards, and validator-set management around one Stake contract.
That can simplify accounting and control, but concentration also raises a quiet question: how much system pressure ends up sitting behind one contract and one stake-weighted validator set?
For DUSK, validator count is the surface metric. Stake concentration is the one I would keep watching.
@Dusk_Foundation #dusk $DUSK
That is the part I think people miss. DUSK security is not really about validator count alone. Ten large provisioners controlling most stake can matter more than 100 small ones with little weight.
The same problem appears with Byzantine stake. Moving from 20% to 30% looks like only +10 percentage points, but it is actually 50% more adversarial capital. And 30% vs 33.3% vs 35% is not a smooth progression either. Crossing the one-third boundary changes the security condition itself.
This is why DUSK’s architecture matters. The older bid/stake/reward structure separated more moving parts, while the current Stake + Transfer model concentrates provisioners, stakes, rewards, and validator-set management around one Stake contract.
That can simplify accounting and control, but concentration also raises a quiet question: how much system pressure ends up sitting behind one contract and one stake-weighted validator set?
For DUSK, validator count is the surface metric. Stake concentration is the one I would keep watching.
@Dusk_Foundation #dusk $DUSK