Skip to content

doc: update the number of misdemeanorThreshold and felonyThreshold #712

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
brilliant-lx merged 1 commit into from
Sep 19, 2025
Merged

doc: update the number of misdemeanorThreshold and felonyThreshold #712

Show file tree
Hide file tree
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
4 changes: 3 additions & 1 deletion docs/bnb-smart-chain/slashing/monitor.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,9 @@ Validators should consistently monitor for potential slashes due to node unavail
As best practice, it is advisable to keep monitoring the event log of the slash contract on the BSC scanner at
<https://bscscan.com/address/0x0000000000000000000000000000000000001001#events>.

You can check your validator's slash indicator in the above contract. Pay attention to values above 30. If it goes over 50, the validator will be slashed. If it goes over 150, the validator will be jailed.
You can check your validator's slash indicator in the above contract. Pay attention to values above 50. If it goes over 200, the validator will be slashed. If it goes over 600, the validator will be jailed.

Pls refer https://docs.bnbchain.org/bnb-smart-chain/slashing/slash-rules/ for more details.

## Unjail Validator

Expand Down
8 changes: 4 additions & 4 deletions docs/bnb-smart-chain/slashing/slash-rules.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,10 +43,10 @@ If the evidence is valid:

There is an internal smart contract that records the missed blocking metrics of each validator.

If a validator misses over 50 blocks in 24 hours, they will not receive the block reward; instead, it will be shared among other validators.
If a validator misses over 200 blocks(governable) in 24 hours, they will not receive the block reward; instead, it will be shared among other validators.

If a validator misses more than 150 blocks in 24 hours:
If a validator misses more than 600 blocks(governable) in 24 hours:

1. **10BNB** would be slashed from the **self-delegated** BNB of the validator
1. **10BNB**(governable) would be slashed from the **self-delegated** BNB of the validator
2. The slashed BNB will be allocated to the credit addresses of validators participating in the next distribution
3. Set the validator `jailed` with a duration of **2 days**, and remove it from the active validator set
3. Set the validator `jailed` with a duration of **2 days**, and remove it from the active validator set