Some of our (Chorus One’s) thoughts on the proposal:
An increase in the slashing penalty for double-signing makes sense, but 20% feels like a bit too much. Something like 10% seems more reasonable. The network is still immature and the most likely reason for a double signing would be an accident, not intentional.
This makes perfect sense and the metric chosen is reasonable.
This is premature in our view. There are not 100 high quality validators at this point. Validators at at the end of the set have hardly any delegations so essentially no influence on the process. This will add communication overhead and increase block times with little added benefit, in our view.
Increasing the community tax also seems premature. Right now, there are no proposals for how to even access and deploy those funds. Let’s figure that out first before putting more capital in there. That should also be tested with small amounts first and the 0.02 are sufficient for that. Once that is working and tested, increasing the tax could definitely make sense.
A few more things:
- We would strongly urge you to make these as separate proposals so people can decide on each one individually. Bundling these in one proposal doesn’t make sense.
- Another parameter that should be changed in our view is downtime slashing. Right now, the barrier for that is ridiculously low. i.e. you can be down for many, many hours without punishment. This should be made much more strict. For example, it could be that if a validator is down more than 20% in a 24h window, they get slashed. (Which after all is a very minor penalty since they can just join the active set again and don’t lose delegators.)