# Transaction Hashes: EVM and Cosmos Formats

1. **EVM Transaction Hash**
   * The EVM transaction hash is computed from the Ethereum-style transaction data, typically encoded using the RLP (Recursive Length Prefix) format.
   * This hash is generated using the Keccak-256 algorithm, which is standard in the Ethereum ecosystem.
   * It uniquely identifies the transaction within the EVM layer and ensures interoperability with Ethereum-compatible tools and platforms.
2. **Cosmos Transaction Hash**
   * Once the EVM transaction is encapsulated within a Cosmos SDK message (e.g., `MsgEthereumTx`), it is assigned a new hash using the Cosmos SDK framework.
   * The Cosmos transaction hash is derived from the serialized byte stream of the entire message, calculated using the SHA-256 algorithm.
   * This hash represents the transaction within the Cosmos ecosystem, ensuring compatibility with Tendermint consensus and other Cosmos-native functionalities.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://mtt-network.gitbook.io/mtt-validator-protocol/node-processing-of-evm-transactions-in-a-cosmos-sdk-compatible-network/transaction-hashes-evm-and-cosmos-formats.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.