The motion is now up for vote, at the operator's request:

> With the advise from Will, after restoring the session key, to make a post in this chat room for the governance team to vote for the removal of the slash, and also allow back into the 1KV program. 
>
> Account: skytron/001 
>
> Hash: EdRrV5evvMhR1mNF25NHBaNgjUgwHtE3puWji6gR9YtUKfp 
>
> New Session key is generated.
>
> This node has been slashed on the era 3329 due to a Detected Precommit equivocation in the finality worker error. I noticed the error and went into github and found out that this may be related to sessionkey. In which, will and some other members confirmed for me that it is. 
>
> I went back and did my diagnostic as I do have another validator node that is used for testing, it was found that likely hood that there were a past session log that indicated that it was cloned after the setup. Nevertheless, I agreed that all nodes shouldn't be clone and that it will not occurred again. Now that I am here, I'm asking the governance team to vote to remove the slash as per advise and understand the next step to allow back into 1KV program. 
>
> I do apologize for the inconvenience, 
>
> Skytron

Link to the message in the Direction Channel: [HERE](https://matrix.to/#/!QXMnIJzxlnVrvRzhUA:matrix.parity.io/$fIA70BdW46m2hj9M8PlysYYGf_R1apdM5Ch1ltdq92E?via=matrix.parity.io&via=matrix.org&via=corepaper.org).

- The operator is requesting a vote from the governance team to remove a slash and allow back into the 1KV program.
- The operator's account is skytron/001 and the hash is EdRrV5evvMhR1mNF25NHBaNgjUgwHtE3puWji6gR9YtUKfp.
- The node was slashed due to an error called Detected Precommit equivocation in the finality worker.
- The operator did some diagnostics and found that there may have been a past session log that caused the error.
- The operator apologizes for the inconvenience and asks for the vote to remove the slash.

#434 Cancellation of slashing event in era 3329