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

Hardware and Operating Requirements

Validators must maintain 24/7 uptime to avoid missing block validation opportunities and to prevent penalties from the network. Using a cloud server is highly recommended to ensure high availability and stability, reducing risks from power outages or hardware failures. Additionally, choosing a cloud provider with a robust Service Level Agreement (SLA) further ensures operational reliability. Continuous uptime guarantees consistent rewards and helps improve the validator's reputation and selection rate in the network.

PreviousWithdrawal CyclesNextMachine Configuration

Last updated 5 months ago