The three offenses that carry penalties
BNB Chain's documentation names three kinds of misbehavior that lead to slashing, and they differ sharply in severity (source: BNB Chain Docs).
| Offense | Penalty | Jail |
|---|---|---|
| Double signing | 200 BNB from the operator's own stake | 30 days |
| Malicious voting | 200 BNB from the operator's own stake | 30 days |
| Missing over 1,000 blocks in 24 hours | 10 BNB from the operator's own stake | 2 days |
Double signing means producing two different blocks at the same height, which is how an operator would attempt to rewrite history. Anyone can submit the evidence, which has to show two block headers at the same height with the same parent, sealed by the same validator with different signatures, within a 24-hour validity window. A valid submission costs the operator 200 BNB, jails it for 30 days and removes it from the active set.
Malicious voting concerns the fast finality mechanism, and carries the same 200 BNB penalty and 30-day jail. Whoever submits valid evidence receives 5 BNB from the system reward contract if the validator was active at the time, which is a bounty designed to make policing worthwhile.
Unavailability is the ordinary offense and by far the most common, and it is graduated across two thresholds, which distinguishes it from the other two.
How downtime is handled
Downtime has two thresholds instead of one, and the difference between them matters to anyone delegating.
Missing more than 333 blocks in 24 hours costs the operator its block rewards for that period, which are shared among the other validators instead. The lost income goes to other validators, and no coins are taken from anyone. This is the level a validator reaches through an ordinary technical problem, and it costs income instead of coins.
Missing more than 1,000 blocks in 24 hours triggers an actual slash: 10 BNB from the operator's self-delegated stake, a 2-day jail, and removal from the active validator set. That is a serious outage rather than a hiccup, and the small penalty combined with the removal is designed to push a persistently unreliable operator out without destroying it.
Both thresholds are governable, meaning they can be changed by on-chain vote, so the current values are worth reading from the chain instead of assumed permanent. PoSA consensus covers how those governance votes are decided.
What a delegator actually loses
This is the part that gets misreported most often.
Every penalty above is taken from the validator's own self-delegated BNB, which is the bond it locked to register, and delegated coins are left alone. Your principal comes through a slash entirely intact, whatever the operator did.
What you lose is rewards, and that happens through three separate routes. A validator missing blocks earns less, so there is less to share. A jailed validator produces nothing at all for the duration, so rewards stop entirely, for 2 days after a downtime slash and 30 days after a double-sign or malicious-vote slash. And a validator removed from the active set stays out until the daily election puts it back, which may take a while if its stake has fallen.
Slashed coins are redistributed to the credit addresses of validators participating in the next distribution, which sends the penalty to operators who did their purpose properly.
The self-delegation requirement is what makes this work as a deterrent. An operator has at least 2,000 BNB of its own locked up (source: BNB Chain Docs), so a 200 BNB penalty removes a tenth of the minimum bond, and the reputational cost of a 30-day removal is larger still.
Reducing your exposure
Four things reduce the chance of a delegation sitting with an operator that ends up penalized.
Check the penalty history, which is recorded on the chain and visible on validator pages, since a past slash is meaningful information about how the operator runs its infrastructure.
Prefer operators with a long operating record, because running reliably through a year of ordinary conditions demonstrates something a new operator has yet to.
Check the tier and the ranking, since Cabinet validators produce more blocks and earn more, and an operator near the boundary of the active 45 can drop out entirely and stop earning. How to choose a validator covers the fields worth comparing.
Consider splitting across operators, which limits the effect of any single one being jailed, at the cost of an extra transaction and a little more to track.
If your validator does get jailed, the response is to redelegate to a healthy one, which moves the stake for a fee of 0.002% and keeps it earning, avoiding the seven-day unbonding period that undelegating would start (source: BNB Chain Docs).
Where this sits among the risks
Slashing is worth understanding properly, and it is rarely the risk that matters most to a delegator.
Price movement dominates everything else on this list. A yield of a few percent is easily outweighed by BNB moving, and rewards are paid in BNB, so the price risk applies to the rewards as well as the principal. The seven-day unbonding period compounds this, since a staked position waits out that week whatever the price does.
Validator penalties, by contrast, cost a delegator some rewards for a bounded period and leave the principal intact. That is a genuine cost, and a much smaller one than the market can impose in a single day. Whether BNB is safe sets these alongside each other.
The reasonable conclusion is to pick a reliable operator, check on it occasionally, and give more attention to how much you stake than to which validator you picked.
Frequently asked questions
Can you lose delegated BNB if a validator is slashed?
Penalties are taken from the validator's own self-delegated stake, so delegated coins are left untouched and your principal survives a slash. What you lose is rewards, through reduced earnings while the operator underperforms and a complete stop while it is jailed. That is the arrangement on BNB Smart Chain, and other networks handle it differently, with some taking a share from delegators too.
What are the actual slashing penalties?
Double signing and malicious voting each cost the validator 200 BNB from its own stake, with a 30-day jail and removal from the active set. Missing more than 1,000 blocks in 24 hours costs 10 BNB, a 2-day jail and removal. A lesser threshold applies at 333 missed blocks in 24 hours, which costs the operator its block rewards for that period without any coins being taken.
What happens to rewards when a validator is jailed?
They stop, because a jailed validator produces no blocks. The duration depends on the offense: 2 days for a downtime slash and 30 days for double signing or malicious voting. The validator is also removed from the active set and has to be re-elected. Redelegating to a healthy operator restarts rewards without triggering the unbonding period.
How do you check a validator's slashing history?
Penalties are recorded on the chain, so they appear on validator pages in the staking application and on block explorers. A history of slashes is meaningful information about how well an operator runs its infrastructure, and so is the length of time it has been operating. Both of those are worth reading before you delegate anything.
What is the difference between jailing and slashing?
Slashing takes coins from the operator's bond, while jailing suspends it from producing blocks for a set period and removes it from the active set. They usually happen together, with the jail duration scaling to the offense. For a delegator, the jail is what stops the rewards, and the slash falls on the operator's own coins.
Should slashing risk stop you staking BNB?
It is one of the smaller considerations, since your principal survives a slash and the cost to you is bounded rewards for a bounded period. Price movement and the seven-day unbonding period both matter more, because a staked position cannot be sold while that period runs. Picking a reliable operator handles most of the slashing exposure, and the sizing decision handles the rest.
Researched and written by the BloFin Academy editorial team with AI-assisted drafting. Updated September 2026. Primary sources include BloFin's Help Center and the BNB Chain documentation. All facts independently verified against cited documentation current as of September 2026.
This article is educational and general in nature, not financial or investment advice. Cryptocurrencies like BNB carry real risks, including price volatility, a seven-day unbonding period, validator penalties pausing rewards, and the chance of an operator leaving the active set. Nothing here is a recommendation to buy, sell, or hold any asset. Do your own research, and consider speaking with a licensed professional before making financial decisions. BloFin does not provide investment advice.