Understanding slashing on VirtEngine

Two classes of validator misbehavior carry slashing consequences: equivocation — signing two different blocks at the same height, the cardinal consensus sin — and extended downtime that degrades network liveness. The economic security framework models slashing penalties explicitly as basis-point penalties on bonded stake.

Slashing is distinct from marketplace enforcement: tenant or provider misconduct flows through the fraud module (x/fraud), while slashing addresses validator protocol violations specifically.

Delegation bonds your tokens to a validator's stake — including its liability. If your validator equivocates or goes dark, delegated stake is slashed alongside self-bonded stake. You are not lending tokens to a validator; you are underwriting its operations.

Unbonding takes 21 days. During that window your stake earns no rewards and remains slashable for offenses the validator committed while your stake was bonded. The delay is not bureaucracy — it is what makes long-range attacks expensive, and the tokenomics framework analyzes exactly that vulnerability class.

Commission is the least informative number on the page. What matters is operational quality:

• Uptime history — downtime costs you rewards even when it isn't slashable
• Key management posture — consensus keys plus VEID encryption keys, both hardened
• Self-bond — validators with skin in the game share your slashing exposure
• Identity-network capacity — VirtEngine validators also run ML scoring duties
• Governance participation — absent validators are a governance liability

VirtEngine validators run consensus and the VEID Network. The second duty brings a second reward stream (the per-epoch pool) but also a second operational surface: encryption key custody and ML scoring workloads. When you evaluate a validator here, you are evaluating both operations.