MTT Validator Protocol
  • Overview
  • Key Features of the Protocol
    • Decentralized and Scalable Consensus
    • Transparent and Fair Validator Incentives
    • Flexible Governance Participation
    • Security and Penalty Mechanisms
    • Automated Validator Monitoring and Reporting
    • Long-Term Network Sustainability
  • Node Processing of EVM Transactions in a Cosmos SDK-Compatible Network
    • Transaction Hashes: EVM and Cosmos Formats
    • Hash Discrepancy: Why Are They Different?
    • Mapping and Storage
  • Reward Mechanism
    • Components of Validator Node Rewards
    • Reward Calculation Method
    • Reward Settlement Time
    • Withdrawal Cycles
  • Hardware and Operating Requirements
    • Machine Configuration
    • Operating System and Network Requirements
  • Slashing Mechanism
    • Reasons for Slashing
    • Execution Details and Timing of Slashing
    • How to Apply for Restoration
  • Operation Manual
    • Node
    • Validator
  • Community
Powered by GitBook
On this page
  1. Slashing Mechanism

Reasons for Slashing

  • Double Signing: If a validator node signs two different blocks at the same time, it is considered malicious behavior, which will result in a slashing of a portion of the node's staked tokens. Double signing is considered an attack on the network and needs to be strictly penalized to ensure network security.

  • Downtime: If a validator node is offline for an extended period and fails to participate in consensus or validate blocks, it can affect the stability of the network. If a node is offline for a certain period (typically exceeding a threshold, such as 24 hours), a portion of the staked tokens will be slashed.

  • Protocol Violations: Any behavior that violates the network protocol (such as tampering with block data or misconduct) will result in penalties for the node. The network will determine the amount of slashing based on the specific violation.

PreviousSlashing MechanismNextExecution Details and Timing of Slashing

Last updated 5 months ago