Signalling proposal to revert the Tombstone and Slashing from Nov 6th block #8647535 network halt and restart due to appHash mismatch event

On November 6th (Block #8647535), the Persistence Core-1 chain halted due to an appHash mismatch caused by differing Golang versions used by the validators.

The Persistence Core-1 and validators responded promptly to tackle the issue and resolve them. During the chain revival, some validators got tombstoned due to double-signing: Fox99, Hashquark, KuCoin, Smart Stake, and Stakin.

After discussing the issue with the community and validators, we have decided to submit a signalling proposal for reverting the tombstoning and slashing events that occurred.

For more details about this event and the proposal, and to join the open discussion, validators, delegators and Persistence community members are invited to read through and participate in the forum thread: https://forum.persistence.one/t/proposal-for-untombstoning-with-unslashing-of-nov-6th-validator-double-signing/122

This proposal is a signalling proposal to revert the tombstoning and slashing events which happened during the network restart of Nov 6th. If this proposal passes, the Core team and the community will have to work on implementing the execution of untombstoning and unslashing, and coordinate a software network upgrade event.

• Vote YES if you support untombstoning and unslashing of the mentioned affected validators
• Vote NO if you think the situation should not be reverted