LogoLogo
Block ExplorerDiscordTwitterMirror
  • What Is Canto?
  • Free Public Infrastructure
    • NOTE
    • Canto Lending Market
    • Canto DEX
  • Canto Neofinance
    • Overview
    • Application Specific Dollar
  • User Guides
    • Connecting to Canto
    • Bridging Assets
      • Bridging to Canto
      • Bridging from Canto
      • Synapse Bridge
      • Celer cBridge
    • Providing Liquidity
    • Lending & Borrowing
    • Staking
    • Governance
  • EVM Development
    • Overview
    • Quickstart Guide
    • NOTE, DEX, and Lending Market
    • Contract Secured Revenue (CSR)
    • Verifying Contracts
    • Contract Addresses
    • Testnet
  • Running a Node
    • Validators
      • Quickstart Guide
      • Useful Commands
      • Snapshots
      • FAQ
      • Troubleshooting
      • Uptime
      • Slashing
    • Archive Node
    • Graph Node (Subgraphs)
  • Technical Reference
    • Application Specific Dollar
      • asdOFT
      • asdRouter
      • asdUSDC
    • Liquidity Coordinator
      • VotingEscrow
      • GaugeController
      • LendingLedger
      • LiquidityGauge
    • Architecture & Design
      • Onboarding Module
      • Gravity Bridge
      • NOTE Design
      • Canto Lending Protocol
      • IBC Token Recovery
    • Governance
      • Governance Module
      • GovShuttle Module
      • Lending Market Governance
    • Tokenomics
    • Audits
Powered by GitBook
On this page
  • Downtime Slashing
  • Consensus Fault Slashing
  • Tombstoning
  1. Running a Node
  2. Validators

Slashing

PreviousUptimeNextArchive Node

Last updated 2 years ago

Canto implements the , which penalizes validators for downtime and consensus faults in various ways:

  • Slashing: the validator loses a percentage of their stake

  • Jailing: the validator is temporarily removed from the validator set

  • Tombstoning (infinite jailing): the validator is irreversibly removed from the validator set

Downtime Slashing

Downtime slashing occurs when a validator fails to sign 3000 consecutive blocks, which corresponds to approximately five hours of downtime.

As a penalty for downtime, validators are:

  • slashed by 0.75%

  • jailed for 1800 seconds (30 minutes)

Consensus Fault Slashing

Consensus fault slashing occurs when a validator commits any kind of consensus fault, intentionally or unintentionally.

As a penalty for consensus faults, validators are:

  • slashed by 5%

  • tombstoned (infinitely jailed)

The most common consensus fault is double signing. Do not attempt to run two validators with the same private key.

Tombstoning

Validators who commit a consensus fault are put in a tombstone state, which means they are irreversibly removed from the validator set and cannot rejoin.

In this case, the only resolution for the validator and its delegators is to unbond and delegate anew pursuant to the 21-day unbonding period.

A tombstoned validator operator may relaunch under a different key, but will have to build up their delegations from scratch.

Cosmos SDK slashing module