POST
/
3997273fc956a67dc6982384500e669e
eth_uninstallFilter
curl --request POST \
  --url https://ronin-mainnet.core.chainstack.com/3997273fc956a67dc6982384500e669e \
  --header 'Content-Type: application/json' \
  --data '{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "eth_uninstallFilter",
  "params": [
    "0x1fb7f4c4e3e6af9d892f657ccaa77a7c"
  ]
}'
{
  "jsonrpc": "<string>",
  "id": 123,
  "result": true
}
Ronin API method that allows for the removal of a filter previously installed on the Ronin node. This method is crucial for resource management, ensuring that filters are only kept as long as they are needed and are cleaned up afterwards.
Get you own node endpoint todayStart for free and get your app to production levels immediately. No credit card required.You can sign up with your GitHub, X, Google, or Microsoft account.
DisclaimerNote 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:Then use the fresh filter ID as the parameter for eth_uninstallFilter.

​
Parameters

  • filter_id — a single filter identifier as a hexadecimal string. This is the ID of the filter that was returned by eth_newFilter or eth_newBlockFilter and is now being uninstalled.

​
Response

  • result — a boolean value indicating the success of the uninstallation. true if the filter was successfully uninstalled, otherwise false. This allows clients to verify that resources have been freed up appropriately.

​
Use case

The eth_uninstallFilter method is used to manage the lifecycle of filters in decentralized applications. It is particularly useful in scenarios where an application dynamically creates filters to track specific events or logs and needs to clean them up after they are no longer necessary, helping to prevent resource leaks and maintain optimal performance.

Body

application/json

Response

200 - application/json

Success status of filter removal

The response is of type object.