LogoLogo
  • Introduction
    • Introducing Othentic Stack
    • Use Cases
  • AVS Framework
    • Abstract
    • Quick Start
    • Othentic CLI
      • Key Management
      • Contracts Deployment
      • Operator Registration
      • AVS Logic Implementation
      • Operator Deposit
      • Node Operators
      • Rewards Distribution
      • P2P Config
        • Custom P2P Messaging
        • P2P Auth Layer
        • Metrics and Monitoring
        • Logging
        • Persistent storage
        • Latency
      • CLI Command Reference
    • Smart Contracts
      • AVS Governance
      • Attestation Center
      • Hooks
        • Task Logic
        • Operator Management
        • Rewards Fee Calculator
      • OBLS
      • Internal Task Handler
      • Othentic Registry
      • Message Handlers
    • Othentic Consensus
      • Abstract
      • Task & Task Definitions
      • Leader Election
      • Proof of Task
      • Execution Service
      • Validation Service
      • Voting Power
      • Rewards
      • Internal Tasks
      • Slashing & Ejection
        • Slashing Modules
        • Custom Slashing
    • FAQ
    • Supported Networks
    • Explainers
      • Networking
      • Multichain
      • Production Guidelines
      • Operator Allowlisting
      • Governance Multisig
  • External
    • AVS Examples
  • GitHub
  • Othentic Hub
Powered by GitBook
On this page
  • Overview
  • Minimum Slashable Stake
  1. AVS Framework
  2. Othentic Consensus

Slashing & Ejection

PreviousInternal TasksNextSlashing Modules

Last updated 9 days ago

Slashing in the Othentic Stack is designed to penalize malicious or faulty behavior from operators. The system executes actions such as slashing and ejection via the .

Overview

The Othentic Stack allows AVS developers to enforce the following penalty mechanisms:

  • Slashing: Deducting a percentage of allocated from misbehaving operators.

  • Ejection: Forcibly removing an operator from the network.

Please note:

  • Ejection is permanent and irreversible. Ejected operators cannot rejoin the AVS

  • Slashing Modules Configuration can be using SLASHING_FLOW .

AVS developers can use two penalty systems:

  • : configurable, deterministic and pre-defined slashing conditions.

    • Operators use the to submit proof of misconduct.

  • : define and enforce arbitrary slashing logic.

It's possible to use just one of the systems, both, or neither.

Minimum Slashable Stake

Minimum Slashable Stake is the minimum amount of stake an Operator must maintain in a specific staking contract to be considered active in an AVS.

This function is only callable by the governance multisig AVS_GOVERNANCE_MULTISIG role.

AVSs can set a minimum slashable amount for a staking contract using function in the AVS Governance.

unique stake
Slashing Modules
Custom Slashing
Challenger System
paused or unpaused
setMinSlashableStakePerStakingContract
Attestation Center