Skip to content

BSC Slash Monitor

Monitor Slash

Generally, without maliciously altering BSC node code or mistakenly running the validator, validators would not typically incur double sign slashes or malicious vote slashes.

Validators should consistently monitor for potential slashes due to node unavailability, as it can lead to slash events.

As best practice, it is advisable to keep monitoring the event log of the slash contract on the BSC scanner at

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.

Unjail Validator

Once a Validator is slashed into a jailed state, the Validator must wait for a specific period before being able to unjail. Once the waiting period elapses, the Validator can access the BNB Staking dApp and proceed to click on the unjail button to initiate the unjail transaction.

BNB Staking dApp: