I am writing to propose an adjustment to the slashing window for validators in order to provide a more reasonable timeframe for validators to recover from periods of downtime. Currently, the minimum block signing requirement is set at 500 blocks per 10,000 blocks, resulting in a maximum downtime of approximately 50 minutes. I suggest increasing this slashing window to 5,000 blocks per 10,000 blocks, allowing validators just over 8 hours (approximately 8 hours and 19 minutes) to resume their operations without being penalized.
There are several reasons why a validator may experience downtime exceeding the current 50-minute limit. These reasons include:
- Validator Operator Availability: Validator operators, like any individuals, need rest and sleep. It is unreasonable to expect them to be available at all times to ensure uninterrupted block signing. By extending the slashing window, we acknowledge the need for validators to have a reasonable break from their responsibilities.
- Traveling Constraints: Validator operators may occasionally need to travel for personal or professional reasons, which could result in temporary unavailability. With an increased slashing window, validators would have more flexibility to manage their operations even during periods of travel.
- Internet and Power Outages: Validators rely on stable internet connections and consistent power supply to fulfill their duties. However, unexpected events such as internet service disruptions or power outages can occur, causing validators to be offline for more than 50 minutes. By extending the slashing window, validators will have additional time to address such technical issues and resume their operations without penalty.
To demonstrate the impact of this proposed change, let us consider the following calculations. Currently, with a minimum signing requirement of 500 blocks (5%) in a 10,000-block window, a validator can be offline for a maximum of 50 minutes. However, by increasi