fix(protocol): fix issue in slash amount calc

[dantaik]

#14216

[adaki2004]

Copying here what i wrote to Discord - about the root cause and possible fix:

We are having a discussion with ZK Pool.
They raised the topic - and this is why we think we see lots of slashes :
They need to stake with MAX_CAPACITY_LOWER_BOUND 128. Which means they have the capacity to prove 128 blcosk in parallel. They say:
128 is the mininum capacity, but in reality it is very unlikely we run 128 provers 🙂
calculated the current block speed, with a few clusters from David  running on parallel, I thought 20 + 20 provers should be enough  for the amount we staked.
Would it make sense to reduce this 128 to 20 for example.. ? I know it might result in 'free market proving' (to not stakers but anyonw) but less slashing.

[adaki2004]

(This min. amount removal helps with reducing/slowing down to 0, but that 128 min required capacity would hurt provers who does not have that parallel capacity)

[dantaik]

Copying here what i wrote to Discord - about the root cause and possible fix:

We are having a discussion with ZK Pool.
They raised the topic - and this is why we think we see lots of slashes :
They need to stake with MAX_CAPACITY_LOWER_BOUND 128. Which means they have the capacity to prove 128 blcosk in parallel. They say:
128 is the mininum capacity, but in reality it is very unlikely we run 128 provers 🙂
calculated the current block speed, with a few clusters from David  running on parallel, I thought 20 + 20 provers should be enough  for the amount we staked.
Would it make sense to reduce this 128 to 20 for example.. ? I know it might result in 'free market proving' (to not stakers but anyonw) but less slashing.

I changed it to 32.