Skip to content

Update validator-performance.md #2720

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
arash009 merged 1 commit into from
Dec 30, 2025
Merged

Update validator-performance.md #2720

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 3 additions & 8 deletions docs/pos/how-to/operate-validator-node/validator-performance.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@

# Validator performance framework

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).
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).

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

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

### Performance benchmark

![Figure: performance benchmark](../../../img/pos/performance-benchmark.png)

To facilitate the transition, there will be a slightly lower benchmark around the first two months while validators become accustomed to the parameters.

* PB1 → 95% of the median average of the last 700 checkpoints signed by the validator set (first 2,800 checkpoints)
* PB2 → 98% of the median average of last checkpoints signed by validator set (continues thereafter)
PB → 95% of median average of last 700 checkpoints signed by the validator set

### Deficient validator process

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

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.

Expand Down