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

# eth\_uninstallFilter

## Summary

Removes a filter and releases the node resources associated with it. The public MegaETH endpoint accepts this standard method even though filter-creation and filter-polling methods are not publicly supported.

## Parameters

| Position | Name       | Type       | Required | Description                                      |
| -------- | ---------- | ---------- | -------- | ------------------------------------------------ |
| `0`      | `filterId` | `QUANTITY` | Yes      | Identifier returned by a filter-creation method. |

## Result

Returns `true` when the filter existed and was removed. Returns `false` when the filter ID was unknown or had already expired. `false` does not mean that `eth_uninstallFilter` itself is unavailable.

## Comparison with Ethereum Standard JSON-RPC

### Ethereum Standard

Clients should uninstall a filter when it is no longer needed so the node can release its resources.

### MegaETH Node Behavior

MegaETH inherits the standard filter-removal handler and returns a boolean indicating whether a filter was removed.

### MegaETH Public Gateway

The method returned `false` for an unknown filter ID on July 24, 2026. The public endpoint returned method-not-found errors for `eth_newFilter`, `eth_newBlockFilter`, `eth_newPendingTransactionFilter`, `eth_getFilterChanges`, and `eth_getFilterLogs` on the same date, so public clients normally use [`eth_subscribe`](/developer-docs/rpc/reference/eth_subscribe.md) instead of filter polling.

## Errors

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

| Code     | Scope            | Message           | When it happens                                     |
| -------- | ---------------- | ----------------- | --------------------------------------------------- |
| `-32602` | Method           | Invalid params    | The filter ID is missing or malformed.              |
| `-32099` | Transport/policy | Payload too large | The request exceeds the public endpoint body limit. |

No method-specific error was observed for a canonical request.

## Examples

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

Capture date: July 24, 2026

Outcome: false

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

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

## Sources

* Spec: [Ethereum Execution APIs, `src/eth/filter.yaml`](https://github.com/ethereum/execution-apis/blob/50d1e5e0b6f5a5046e45421e5c84497ab6e55e6c/src/eth/filter.yaml)
* 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_uninstallfilter.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.