Need a design proposal that covers all the slashing conditions

[aeyakovenko]

Problem

Slashing is something that is mentioned in fork selection, leader rotation. But there is no explicit list of how slashing proofs work for each slashable offense.

Proposed Solution

Write the doc. Should cover:

• slashing due to contentious fork at lockout.
• slashing due to voting back in time
• duplicate ledger generation

The slashing proofs need to be fast to verify by the network.

[mvines]

"a 72 hour freeze is prolly what we should start with" - anonymous
(for slashable votes)

[aeyakovenko]

maybe a 1-5% slashing as well.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

[stale]

This stale issue has been automatically closed. Thank you for your contributions.

[github-actions]

This issue has been automatically locked since there has not been any activity in past 7 days after it was closed. Please open a new issue for related bugs.