> For the complete documentation index, see [llms.txt](https://docs.megaeth.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.megaeth.com/developer-docs/rpc/reference/eth_protocolversion.md).

# eth\_protocolVersion

## Summary

Returns the Ethereum protocol version reported by the connected node. The public MegaETH endpoint supports this legacy compatibility method.

## Parameters

None.

## Result

The result is a hexadecimal `QUANTITY`. Do not confuse this compatibility value with the MegaETH chain ID or network ID.

## Comparison with Ethereum Standard JSON-RPC

### Ethereum Standard

The legacy method reports an Ethereum wire-protocol version and takes no parameters.

### MegaETH Node Behavior

MegaETH exposes the inherited compatibility method through the `eth` namespace.

### MegaETH Public Gateway

The gateway treats this response as immutable and may cache it. Callers should not use this value for chain selection; use [`eth_chainId`](/developer-docs/rpc/reference/eth_chainid.md) instead.

## Errors

The `| Scope |` column distinguishes request failures from gateway policy errors.

| Code     | Scope            | Message           | When it happens                                     |
| -------- | ---------------- | ----------------- | --------------------------------------------------- |
| `-32602` | Request          | Invalid params    | Unexpected parameters are supplied.                 |
| `-32099` | Transport/policy | Payload too large | The request exceeds the public endpoint body limit. |

No method-specific errors were observed.

## Examples

Endpoint: `https://mainnet.megaeth.com/rpc`

Capture date: July 24, 2026

Outcome: success

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "eth_protocolVersion",
  "params": []
}
```

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "result": "0x5"
}
```

## Sources

* Probe: MegaETH Mainnet public endpoint, July 24, 2026


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.megaeth.com/developer-docs/rpc/reference/eth_protocolversion.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.