Thank you for initiating this important discussion on validator accountability and network performance. At Govmos, we recognize the value of raising standards but also acknowledge the valid concerns raised regarding the operational challenges of stricter parameters.
To strike a better balance, we propose a more gradual approach:
- Instead of a 4x reduction in the SignedBlocksWindow (from 8192 to 2048), we suggest halving it to 4096 first. This smoother adjustment would allow time to assess its impact while ensuring it doesn’t disproportionately penalize legitimate infrastructure maintenance.
- Following this, a performance evaluation should take place to ensure only underperforming actors are affected, not validators performing routine maintenance responsibly.
- Upon confirming that the changes effectively address poor-performing validators, we propose introducing a minimal slashing penalty to add a financial disincentive for repeated downtime. This step would further encourage accountability without prematurely affecting compliant operators.
We believe this moderate, step-by-step approach is both pragmatic and fair, allowing the community to achieve better performance standards while safeguarding validators’ operational needs.
Thank you for reading,
The Govmos Team
