> 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_unsubscribe.md).

# eth\_unsubscribe

## Summary

Cancels an existing subscription so that no further events are sent.

The public MegaETH endpoint supports this method. The standard, node, and gateway layers below identify behavior that differs from a generic Ethereum endpoint.

## Parameters

**`subscriptionId`** Data **REQUIRED**

Subscription ID returned by `eth_subscribe`.

## Result

**`result`** boolean

`true` if the subscription was found and cancelled; `false` if the ID was not active.

## Comparison with Ethereum Standard JSON-RPC

### Ethereum Standard

`eth_unsubscribe` is part of the commonly implemented Ethereum WebSocket subscription API, but it is not specified by the core execution JSON-RPC API.

### MegaETH Node Behavior

The node cancels a subscription in the WebSocket session that created it. Subscription IDs are connection-scoped.

### MegaETH Public Gateway

The public method is WebSocket-only. The gateway keeps subscription ownership per connection and rejects attempts to cancel a subscription from another session.

## Errors

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

| Code     | Scope   | Message         | When it happens                                    |
| -------- | ------- | --------------- | -------------------------------------------------- |
| `-32602` | Request | Invalid params  | Subscription ID parameter is missing               |
| `-32600` | Request | Invalid request | Subscription was created by a different connection |

See also [Error Codes](/developer-docs/rpc/error-codes.md).

## Examples

Endpoint: `wss://mainnet.megaeth.com/ws` (WebSocket)

Capture date: July 24, 2026

Outcome: success

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "eth_unsubscribe",
  "params": ["0xaec58cfc2dc41f873fc37d6c871230c1"]
}
```

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

## Sources

* Spec: EIP-1474 for JSON-RPC framing and error conventions; this method is an extension or legacy compatibility method.
* Code: `git@github.com:megaeth-labs/mega-reth.git @ ab60376631228edab3a6df180f295280bad26e93: crates/megaeth/rpc/src/eth/api.rs`
* Code: `git@github.com:megaeth-labs/mega-rpc.git @ 06aa35aa95d569c227cc25d2aa12834eb0458aa0: workers/src/rpc-gateway/websocket-session.ts`
* 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_unsubscribe.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.