> ## Documentation Index
> Fetch the complete documentation index at: https://docs.chainstack.com/llms.txt
> Use this file to discover all available pages before exploring further.

# eth_uninstallFilter | Fantom

Fantom API method used to remove a filter previously created using one of the following methods:

* [eth\_newFilter](/reference/fantom-newfilter)
* [eth\_newPendingTransactionFilter](/reference/fantom-newpendingtransactionfilter)
* [eth\_newBlockFilter](/reference/fantom-newblockfilter)

Upon successful execution, the filter is removed and will no longer emit events.

This method can be useful for optimizing resource usage when a developer no longer needs to monitor certain events or blocks. It can also be used to clean up unused filters in order to reduce clutter in the client-side filter list.

<Warning>
  **Disclaimer**

  Note that the default interactive example in this page will not work as the filter will be expired.

  To test `eth_uninstallFilter` in this page, first create a new filter using one of the following:

  * [eth\_newFilter](/reference/fantom-newfilter)
  * [eth\_newPendingTransactionFilter](/reference/fantom-newpendingtransactionfilter)
  * [eth\_newBlockFilter](/reference/fantom-newblockfilter)

  Then use the fresh filter ID as the parameter for `eth_uninstallFilter`.
</Warning>

<Check>
  **Get your own node endpoint today**

  [Start for free](https://console.chainstack.com/) and get your app to production levels immediately. No credit card required.

  You can sign up with your GitHub, X, Google, or Microsoft account.
</Check>

## Parameters

* `string` — the filter ID that you want to uninstall

## Response

* `boolean` — a boolean value indicating whether the filter was successfully uninstalled. `true` if successfully removed, and `false` if not.

## `eth_uninstallFilter` code examples

<Note>
  Note that the `web3.eth.filter` methods have been deprecated and replaced with the `web3.eth.subscribe` in web3.js. See [web3.js subscriptions](/reference/ethereum-web3js-subscriptions-methods).
</Note>

<CodeGroup>
  ```javascript ethers.js theme={"system"}
  const ethers = require('ethers');
  const NODE_URL = "CHAINSTACK_NODE_URL";
  const provider = new ethers.JsonRpcProvider(NODE_URL);

  async function removeFilter(filter) {
    try {
      const removed = await provider.send('eth_uninstallFilter', [filter]);
      console.log(removed); // Log whether the filter is removed
    } catch (err) {
      console.error(err); // Handle errors that may occur
    }
  }

  const filterId =  '0x4e7ef166cd43f188b0f8f9e218966a8f' //'YOUR_FILTER_iD'
  removeFilter(filterId)
  ```

  ```python web3.py theme={"system"}
  from web3 import Web3  
  node_url = "CHAINSTACK_NODE_URL" 
  web3 = Web3(Web3.HTTPProvider(node_url))

  def remove_filter(filter_id):
      try:
          removed = web3.eth.uninstall_filter(filter_id)
          return removed
      except Exception as e:
          print(e)

  filter_id = '0x0'
  print(remove_filter(filter_id))
  ```
</CodeGroup>

## Use case

One use case for `eth_uninstallFilter` is to optimize resource usage in a DApp. When a DApp needs to monitor events on the blockchain, it can create a filter using [eth\_newFilter](/reference/fantom-newfilter),[eth\_newPendingTransactionFilter](/reference/fantom-newpendingtransactionfilter), or [eth\_newBlockFilter](/reference/fantom-newblockfilter) to listen for specific events or blocks.

However, once the DApp no longer needs to monitor these events or blocks, it can use `eth_uninstallFilter` to stop watching for them. By doing so, the DApp can reduce the number of active filters and free up resources, such as network bandwidth and computational power, that would otherwise be used to maintain the filter.

For example, let's say that a DApp is monitoring incoming blocks, logs batches of 50 blocks, and then uses `uninstallFilter` to remove the filter.


## OpenAPI

````yaml /openapi/fantom_node_api/eth_uninstallFilter.json POST /4ab982aa70a7baead515ffdb5915df3f
openapi: 3.0.0
info:
  title: Fantom Node API
  version: 1.0.0
  description: This is an API for interacting with a Fantom node.
servers:
  - url: https://fantom-mainnet.core.chainstack.com
security: []
paths:
  /4ab982aa70a7baead515ffdb5915df3f:
    post:
      summary: eth_uninstallFilter
      operationId: uninstallFilter
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                jsonrpc:
                  type: string
                  default: '2.0'
                method:
                  type: string
                  default: eth_uninstallFilter
                params:
                  type: array
                  items:
                    type: string
                    title: Filter ID
                  default:
                    - '0xbdc5b4b99ca699e1d734fc4202afee79'
                id:
                  type: integer
                  default: 1
      responses:
        '200':
          description: Boolean value indicating if the filter was removed or not.
          content:
            application/json:
              schema:
                type: object
                properties:
                  jsonrpc:
                    type: string
                  id:
                    type: integer
                  result:
                    type: boolean

````