Skip to content

Commit e6c8e04

Browse files
authored
Merge pull request #2720 from Vasanti01/patch-1
Update validator-performance.md
2 parents 0f9ab16 + 0c939d6 commit e6c8e04

File tree

1 file changed

+3
-8
lines changed

1 file changed

+3
-8
lines changed

docs/pos/how-to/operate-validator-node/validator-performance.md

Lines changed: 3 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11

22
# Validator performance framework
33

4-
This is a guide to help users understand the validator performance parameters the community agreed to in [PIP-4](https://snapshot.org/#/polygonvalidators.eth/proposal/0x1e9d79b6406870ebd0b66ac256b59012f97f3f4d652052681c6fb1077e251804).
4+
This is a guide to help users understand the validator performance parameters the community agreed to in [PIP-9](https://forum.polygon.technology/t/pip-9-performance-benchmark-adjustment/11387) and [PIP-4](https://forum.polygon.technology/t/pip-4-validator-performance-management/9956).
55

66
These parameters and the related health statuses help provide information about validator performance against a defined performance benchmark.
77

@@ -17,18 +17,13 @@ A validator’s performance is measured based on the checkpoints it signed over
1717

1818
### Performance benchmark
1919

20-
![Figure: performance benchmark](../../../img/pos/performance-benchmark.png)
21-
22-
To facilitate the transition, there will be a slightly lower benchmark around the first two months while validators become accustomed to the parameters.
23-
24-
* PB1 → 95% of the median average of the last 700 checkpoints signed by the validator set (first 2,800 checkpoints)
25-
* PB2 → 98% of the median average of last checkpoints signed by validator set (continues thereafter)
20+
PB → 95% of median average of last 700 checkpoints signed by the validator set
2621

2722
### Deficient validator process
2823

2924
* If validator <PB in the MP → Grace Period 1 (“GP1”).
3025
* If validator is in GP and <PB after 700 checkpoints → Notice of Deficiency (“NOD”), validator enters into Grace Period 2 (“GP2”).
31-
* If validator is in GP2 and <PB after 700 checkpoints → Final Notice (“FN”), the validator will be unstaked per PIP-4.
26+
* If validator is in GP2 and <PB after 700 checkpoints → Final Notice (“FN”), the validator will be unstaked per PIP-4 and PIP-9.
3227

3328
Each GP is an additional 700 checkpoints, allowing a validator to bring their performance back above the PB. If the deficiency is corrected within the GP, there will be no further action. Failure to match, or out perform the performance benchmark, at the end of GP2 will result in a public NOD that will be displayed on the staking dashboard.
3429

0 commit comments

Comments
 (0)