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. Node Processing of EVM Transactions in a Cosmos SDK-Compatible Network

Mapping and Storage

To maintain cross-ecosystem compatibility and traceability, the network implements the following mechanisms:

  1. Encapsulation

    • The original EVM transaction is encapsulated within a MsgEthereumTx message in the Cosmos SDK.

    • This allows the Cosmos network to process the transaction while preserving its EVM-specific attributes.

  2. Indexing

    • Nodes store both the EVM transaction hash and the Cosmos transaction hash.

    • These hashes are linked via an indexing mechanism to enable seamless querying and retrieval:

      • Users querying by EVM hash can retrieve the corresponding Cosmos transaction and vice versa.

PreviousHash Discrepancy: Why Are They Different?NextReward Mechanism

Last updated 5 months ago