LogoLogo
  • Introduction
  • Running Tellor Layer
    • Getting Started
    • Bridging Sepolia TRB
      • Bridge TRB back to Sepolia
      • Manual Generation of Bridge Query Data / IDs
    • Managing Accounts
    • Node Setup
      • Peers List & Public RPCs
      • Cosmovisor Sync
      • State Sync Troubleshooting / Resetting Chain Data
      • Example .service Files
    • Run a Layer Validator
      • Slashing Rules for Validators
    • Become a Data Reporter
      • Unjail Your Reporter
    • Command Line Usage
      • Query the Chain
      • Creating Transactions
      • Delegate to a Validator
      • Select a Reporter
  • Disputes and Reporter Governance
  • No-Stake Reporting
  • Using Tellor Data
    • Relay Data to EVM Chains
    • Integrating Tellor Data
    • Integrate Tellor on a New Chain
Powered by GitBook
On this page
  • Context
  • Slashing, Jailing, and Tombstoneing
  • Liveness (inactivity):
  • Check Your Validator's Status
  • How to Unjail
  1. Running Tellor Layer
  2. Run a Layer Validator

Slashing Rules for Validators

PreviousRun a Layer ValidatorNextBecome a Data Reporter

Last updated 21 days ago

Context

Tellor inherits validator slashing mechanisms from CometBFT. A detailed understanding can be found in the .

Slashing, Jailing, and Tombstoneing

There are two basic reasons that a validator may be automatically slashed, jailed or tombstoned: liveness and double signing.

Liveness (inactivity):

If your validator fails to sign for 500 blocks (e.g. the validator node is down for 500 blocks), the validator will be automatically jailed. At the time of writing layertest-4 has a 1.8s average block time, so it takes approximately 15 minutes of inactivity before a validator is jailed.

The penalty for inactivity is 1% of bonded tokens. Liveness slashes do not lead to a tombstombing.

If your node is Jailed for inactivity, you can simply "unjail" it via cli on the host machine:

Double Signing:

Unjustified pre-commits (double signs) are rare, and the penalty is severe. If a double sign is detected the validator is automatically slashed up to 50% and tomestoned, while their delegators are forced to unbond or redelegate their token voting power. A “tombstoned" validator key can never be used again. The validator may rejoin the network using another node key, but they will have to earn back the trust of any delegators they previously had.

Warning: It is possible to double sign blocks accidentally during complex operations like migrating a validator node to a different machine. Always be 100% sure that the layer node process on the old machine is dead before starting it up on the new machine!

Check Your Validator's Status

You can check your validator's status on theor via cli:

./layerd query staking validator ACCOUNT_NAME

"status: 2" means that you are jailed.

How to Unjail

Unjail your validator with the command:

./layerd tx slashing unjail --from YOUR_ACCOUNT_NAME --chain-id layertest-4 --fees 5loya --yes
cosmos SDK documentation
block explorer