 **motion 295** is now up for vote. The motion proposes the cancellation of 115 slashes that happened in era 2,249.   

v9010 runtime upgrade introduced some changes to elections to ensure redundancy in the case that a solution did not get submitted to the chain. Validators running with Interpreted wasm execution, slower hardware, and / or older client releases were not able to process election solutions within a bounded time window, and thus continually would try and process election solutions. This resulted in Off Chain Workers being not available to submit heartbeats, making validators that did not produce any blocks in the session offline. Enough validators were not running with proper performance (wasm execution parameters, lower end hardware, or older client versions), and as a result, exceeded the threshold for liveness slashing. 

  Please vote at your convenience!

 Cancel enactment of a deferred slash.

 Can be called by the `T::SlashCancelOrigin`.

 Parameters: era and indices of the slashes for that era to kill.

 # <weight>
 Complexity: O(U + S)
 with U unapplied slashes weighted with U=1000
 and S is the number of slash indices to be canceled.
 - Read: Unapplied Slashes
 - Write: Unapplied Slashes
 # </weight>

Problem Statement:
- The problem is that the v9010 runtime upgrade caused issues with elections, leading to validators being offline and exceeding the threshold for liveness slashing.

Significance:
- The significance of this problem is that it affects the availability and performance of validators, potentially impacting the overall security and stability of the network.

Proposed Solution:
- The proposed solution is to cancel the 115 slashes that occurred in era 2,249.

Expected Outcomes:
- The expected outcome is to address the issue caused by the v9010 runtime upgrade and prevent further liveness slashing.

#295 Cancellation of 115 slashes that happened in era 2,249