Is Slashing Coming to Solana? What It Means for Validators and Delegators

TL;DR

• Slashing is not live on Solana today, but it is being built and is targeted around 2026.
• The Validator Admission Ticket (VAT) introduced with Alpenglow is not slashing. It is a 1.6 SOL per-epoch admission fee that is burned, replacing the old roughly 2 SOL per-epoch on-chain voting cost.
• SIMD-0204 builds the detection and recording layer that logs evidence of slashable behavior on-chain, specifically for duplicate block production.
• SIMD-0212 proposes the penalty economics, including burning delegated stake at epoch boundaries. It is still under community discussion and is not finalized, so its penalty design should be read as proposed, not settled.
• For delegators, validator selection becomes a direct risk factor, not just a rate factor. Everstake operates non-custodial validators across 130+ networks.

Is slashing live on Solana today?

Slashing is not active on Solana right now, but the protocol work to introduce it is underway and targeted around 2026. There is no programmatic mechanism today that automatically removes delegated stake as a penalty for validator misbehavior.

The confusion often comes from recent changes that might become active with Alpenglow. Those changes are altering validator economics, but they will not add a stake penalty directly.

Two separate SIMD proposals carry the actual slashing work forward. One handles detection, the other proposes the penalty design, and both are under discussion.

What slashing is, in plain terms

Slashing is a protocol-level penalty in proof-of-stake networks that removes a portion of staked tokens when a validator commits a serious fault. It exists to make attacks and negligence costly, aligning operator behavior with network security.

In a typical proof-of-stake design, two fault classes draw penalties:

• Liveness faults, such as prolonged downtime, duplicate block production or missed duties.
• Safety faults, such as double-signing or equivocation that can threaten consensus.

On Solana specifically, the proposed model focuses penalties on provable, on-chain evidence of misbehavior. The design separates the act of recording a fault from the act of penalizing it, which is why the work is split across two proposals.

The VAT is not slashing

The Validator Admission Ticket (VAT) is an admission fee, not a penalty. It is a 1.6 SOL per-epoch cost that is burned, and it replaced the old roughly 2 SOL per-epoch on-chain voting cost that validators previously paid.

A burned admission fee is a known, fixed operating cost per epoch, while slashing is a conditional penalty triggered only by specific faults.

Item	VAT (Alpenglow)	Slashing (proposed)
Type	Admission fee	Conditional penalty
Amount	1.6 SOL per epoch, burned	Proposed, not finalized
Trigger	Participation each epoch	Provable misbehavior
Predictable	Yes, fixed per epoch	No, event-driven
Status	to go live with Alpenglow	Targeted around 2026

For Alpenglow and VAT context, see Solana’s Alpenglow roadmap.

The slashing track: SIMD-0204 vs SIMD-0212

SIMD-0204 and SIMD-0212 address two different halves of slashing. SIMD-0204 builds the detection and recording layer, while SIMD-0212 proposes the penalty economics that act on recorded evidence.

SIMD-0204 is the evidence layer. It defines an on-chain mechanism to log proof of slashable behavior, creating a verifiable record of faults.

SIMD-0212 is the penalty layer. It proposes how recorded faults translate into consequences, including burning delegated stake at epoch boundaries.

SIMD-0212 is still under active community discussion and has not been finalized. Its penalty parameters should be read as proposed, not settled, and specific percentages are not confirmed.

What is at stake for delegators

Delegators face a new, direct risk once slashing is live: a validator’s faults could reduce delegated stake, not just affect the rate of rewards. Penalties under SIMD-0212 are designed to scale with the severity and correlation of the offense.

The proposed scaling spans a wide band of outcomes:

• Minor offenses carry little or no penalty.
• Isolated, low-correlation faults sit lower on the scale.
• Correlated or severe violations could lead to full slashing of delegated stake.

These bands describe the proposed direction of SIMD-0212, not finalized numbers. The takeaway is structural: delegated stake can be exposed to a validator’s operational mistakes.

The “desperado” edge case

The “desperado” case is an open question in SIMD-0212 about a fully-slashed validator that remains in consensus for an epoch and a calculation lag. A validator already slashed to zero may have nothing further to lose during the remainder of that epoch and the at-risk validator continues participating with full (not-yet-reduced) consensus weight during that lag window.

This matters because penalty design assumes validators respond to economic deterrence. A validator with no remaining stake at risk may behave unpredictably until it exits at the epoch boundary.

Resolving this edge case is part of why SIMD-0212 remains under discussion. The handling of a zero-stake validator inside an active epoch is not settled.

How a serious operator prevents slashing risk

Under Solana’s proposed slashing model, the penalty applies to safety faults: provable violations like duplicate block production and, after Alpenglow, equivocation (casting conflicting votes).

A serious operator’s job is therefore to make safety faults effectively impossible, while still running clean infrastructure to protect rewards and uptime.

Core mitigation practices include:

1. Key management that guarantees the same signing key is never active in two places at once (the root cause of most double-signing incidents.)
2. No equivocation, enforced in tooling that blocks a validator from signing conflicting blocks or votes, rather than relying on operator discipline alone.
3. Infrastructure and client hygiene, including tested upgrades, staged rollouts, and no single points of failure, so a migration or client bug doesn’t trigger a double-sign.
4. Monitoring and alerting on uptime, missed duties, and anomalies primarily to protect rewards and catch problems early, with the added benefit of surfacing the kind of misconfigurations that can lead to safety faults.

Correlation is the aggravating factor in the proposed penalty design: the more stake that commits the same fault in the same window, the steeper the slash. That makes infrastructure diversity a direct risk-reduction lever varied clients, regions, and failure domains reduce the chance of the domino effect and pushes the penalty up the curve.

Everstake approaches these practices through non-custodial validator infrastructure operated historically across 130+ networks.

Read more about slashing prevention in our dedicated material on Institutional Guide for Slashing Prevention.

Implications for validator selection

For institutions and retail users validator selection becomes a direct risk factor under slashing. The choice of operator can determine whether delegated stake is exposed to avoidable faults.

A practical operator-diligence checklist covers:

• Uptime track record and historical reliability.
• Key management practices and double-sign protection.
• Infrastructure hygiene, including client diversity and upgrade discipline.
• Monitoring and incident response maturity.
• Transparency about operations and slashing protections.

Everstake has operated non-custodial validators across 130+ networks, while being one of the Solana earliest validators and has supported every major protocol change since.

Everstake is cultivating its Solana expertise through products such as Blockspace. Blockspace packages the Solana inbound path as products, giving validators, operators and teams a structured way to access block production and transaction inclusion on the network.

We remain committed to Solana and are preparing for the slashing track, Alpenglow changes, and the institutional roadmap the network has boarded. Tracking SIMD-0204 and SIMD-0212 closely lets us adapt validator operations as detection and penalty rules are finalized.

FAQ

Is slashing live on Solana?

No, slashing is not live on Solana today. It is being built and targeted around 2026, with detection and penalty work split across SIMD-0204 and SIMD-0212.

Is the VAT a form of slashing?

No, the Validator Admission Ticket is not slashing. It has a 1.6 SOL per-epoch admission fee that is burned, replacing the old roughly 2 SOL per-epoch on-chain voting cost.

What is SIMD-0212?

SIMD-0212 is the proposal for Solana slashing penalty economics. It proposes burning delegated stake at epoch boundaries. As of June 2026, it remains under community discussion rather than finalized.

What does SIMD-0204 do?

SIMD-0204 builds the detection and recording layer for slashable behavior. It has an on-chain mechanism that logs evidence of faults, separate from the penalty economics in SIMD-0212.

Can delegators lose stake to slashing?

Under the proposed design, delegators could lose stake if their validator commits a serious fault. Penalties in SIMD-0212 are designed to scale, with correlated or severe violations carrying the highest exposure.

How do validators avoid slashing?

Validators avoid slashing through key management, client and infrastructure hygiene, monitoring, and no double-signing. Everstake applies these practices across non-custodial validators on 130+ networks.

Does the VAT replace the old voting cost?

Yes, the VAT replaces the prior on-chain voting cost. The old cost was roughly 2 SOL per epoch, and the VAT is 1.6 SOL per epoch, burned.