Slashing
Origin:
composes, a mechanism popularized by Ethereum's Casper FFG design, not a Solidus original. Solidus status:testnet, equivocation and downtime are treated as slashable in the shipped engine; the stake at risk has no real economic value yet.
Slashing is a validator's punishment for provably breaking the rules: the network destroys or confiscates part of their bonded stake. It's the enforcement half of stake-based consensus, bonding stake only deters bad behavior if breaking the rules can actually cost the validator something concrete. The most commonly slashed offenses across blockchains are "equivocation" (signing two conflicting blocks or votes in the same round, the digital equivalent of a Byzantine general sending contradictory orders) and extended downtime (failing to participate when selected, which degrades the network without necessarily being malicious).
Where it comes from
The term and mechanism were formalized for practical use by Vitalik Buterin and Virgil Griffith's 2017 Casper FFG paper, which introduced slashing conditions as the accountability layer for Ethereum's eventual move to proof-of-stake. Cosmos/Tendermint-based chains adopted similar slashing models around the same period. Solidus didn't originate the mechanism; it wrote its own detection logic for the specific conditions its consensus engine checks.
What's actually enforced today
The shipped consensus engine treats two things as slashable: double-signing/equivocation (a validator signing two different proposals for the same round) and extended downtime. Both are checked in the running code. What is not currently enforced is the fuller model described in Solidus's public documentation, a reputation score that rises and falls with behavior, censorship-specific slashing (penalizing a validator for provably refusing to include valid transactions), and a formal governance appeals process. Those remain target design.
There's also a more basic honesty point: because no $SLDS token has ever been publicly distributed (see Validator), any stake slashed today only adjusts a testnet-internal number. Nobody has actually lost anything of real economic value to a Solidus slashing event, because nothing of real economic value is staked yet.
Check it yourself
There is no independently reproducible slashing event to point to today: that would require a live stake with real value and a third party willing to misbehave against it, neither of which exist yet. What you can check is the detection code itself: the equivocation check lives in the public protocol repository's consensus crate.
Related terms: Validator · HotStuff · BFT · Proof-of-Identity
Where it comes from
Someone else specified this. Solidus assembles it.
Slashing, destroying or confiscating part of a misbehaving validator's bonded stake, was popularized by Ethereum's Casper FFG design (Vitalik Buterin and Virgil Griffith, 2017) and is now standard across Cosmos/Tendermint chains and Ethereum's own beacon chain. Solidus composes the general pattern; its consensus engine implements its own equivocation/double-signing and downtime checks rather than reusing another chain's slashing module.
How to check this
Running on the test network. Not mainnet.
Not independently reproducible yet. There is no live stake with real economic value to demonstrate a slash against, and no third party has triggered or publicly observed one on the testnet. The equivocation/double-signing check is visible in the public protocol repository's consensus crate.