Back to Blog
SIMD-0204: The First Step To Slashing On Solana
Written By
Rex St. John
December 16, 2024
Slashing On Solana
Over the next few months, a series of SIMDs and discussions are planned by the core engineering team at Anza in collaboration with ecosystem partners and developers to define a path to slashing on Solana. The first step in this direction is SIMD-0204: Slashable Event Verification. This article will cover SIMD-0204 as well as follow on steps and what to expect going forward.
Motivation
In blockchain protocols, slashing is a penalty mechanism that punishes validators who behave maliciously or break protocol rules. When a validator is "slashed," they typically lose some or all of their staked tokens. This creates a strong economic incentive for validators to follow the rules and maintain network security. While many blockchain networks like Ethereum already implement slashing, this proposal represents a significant step for Solana as it introduces the groundwork for slashing capabilities.
A Closer Look At SIMD-0204: Slashable Event Verification
SIMD-0204 introduces a new on-chain program in Solana that can verify and record when validators commit violations of the protocol rules. Importantly, this initial implementation only focuses on detecting and recording violations - it doesn't yet implement actual penalties or token slashing.
The primary focus is on catching what's called "duplicate block" violations. This happens when a validator creates more than one version of the same block, which could potentially lead to network inconsistencies or attacks. The program can verify proof of these violations and create permanent records on the blockchain that can't be altered or disputed.
The program (S1ashing11111111111111111111111111111111111
) verifies several things: It checks that the violation actually occurred, confirms the validator really signed both blocks (using their cryptographic signature), and ensures the proof is submitted within a reasonable timeframe (within one epoch, or a set period in Solana's timeline).
Once verified, the program creates a permanent record of the violation in a special account on the blockchain. This record includes important details like which validator committed the violation, when it happened, and the full proof of their misbehavior.
For further details, view the SIMD itself linked below.
Why It Matters
This proposal is particularly interesting because it sets up the infrastructure needed for future slashing implementations. While it doesn't immediately punish validators for misbehavior, it creates the necessary foundation for future proposals that will implement actual penalties.
What Comes Next
Rolling out slashing broadly in Solana will involve ongoing community discussion. Logging incidents of slashing via SIMD-0204 and agreeing what constitutes slashing represents the first step. Once this has been agreed upon, the following will occur:
SIMD on implementation of Slashing [extensive community input expected]
A period of communication with key stakeholders, especially large validators
Governance Vote
Addition to the Activation Gate schedule
General Rollout
Closing Thoughts
The design shows careful consideration for security and permanence. The program itself can't be modified except through validator software updates, ensuring that malicious actors can't tamper with the slashing verification system. This conservative approach - first implementing detection and recording, then later adding penalties - allows the Solana community to carefully consider and discuss the economic implications of different slashing penalties before implementing them.
Links
Timeline
2024-09-29: Initial Proposal Created
2024-10-03: Proposal updated to add datacheck, three epoch window rationale
2024-10-04: Instructions sysvar
Credits
Thanks to everyone who took the time to give feedback on this post including Wen Xu, Ashwin and Ben Hawkins: