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

Hash Discrepancy: Why Are They Different?

The EVM and Cosmos transaction hashes represent the same transaction but differ due to distinct data structures:

  1. EVM Transaction Hash

    • Focuses solely on the original Ethereum-formatted transaction data.

    • Reflects the transaction’s structure and content as processed by the EVM layer.

  2. Cosmos Transaction Hash

    • Includes the EVM transaction as part of a broader Cosmos message structure.

    • May incorporate additional metadata such as gas settings and Tendermint-specific elements.

As a result, the hashing inputs vary, leading to different hash outputs for the same underlying transaction.

PreviousTransaction Hashes: EVM and Cosmos FormatsNextMapping and Storage

Last updated 5 months ago