Skip to content

Latest commit

 

History

History
37 lines (22 loc) · 1.97 KB

REP-0017.md

File metadata and controls

37 lines (22 loc) · 1.97 KB

REP-0017: Propose New Slashing Rules

Preamble

REP-0017
Title: Propose New Slashing Rules
Author: Maxbrand99 and phucthai
Type: Standard
Status: Approved
Created: 2024-06-19

Abstract

REP-0017 describes new slashing rules to go into effect with RVs

Rationale

With the migration from Standard Validators (SVs) to Rotating Validators (RVs) it becomes more important than ever to have strict rules with regards to slashing. The changes to the rules to make them more forgiving made sense when we were starting on DPoS as it allowed us to have more of a room for error with new software. The risks caused by forgiving slashing rules were mitigated by the limit of only 10 SVs being allowed combined with an incredibly high barrier of entry to become one of the SVs (upwards of 8 million RON). With the change to RVs, the barrier for entry is now 1/32 as difficult. I believe that increasing the slashing rules would act as a good deterrent to stop users that should not be running a node (due to lack of technical knowledge).

Specification

From phucthai in the ronin validator chat: (check UpdatedSlashing.png)

  • Block Miss Penalty: If a validator misses 50 blocks in a day, it will be slashed and will not receive rewards for that day (similar to the current Tier 1 slashing). In the new design, the slashed validator will also be banned from being selected as a block producer. This eliminates Tier 2 slashing because a slashed validator cannot produce new blocks, thus cannot miss additional blocks.
  • Repeated Slashing Penalty: If a validator is slashed three times within a seven-day period, it will incur a penalty of 1,000 self-staked RON. This rule aims to penalize validators running on low-spec machines that consistently get slashed.

Security analysis

This encourages validators to maintain good service and uphold high performance standards for the Ronin chain.

License

The content is licensed under CC0.